Logix5000 Controllers Controller Information and Status
Important User InformationSolid 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-11 available from your local Rockwell Automation sales office or online at httpliteraturerockwellautomationcom) 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
Allen-Bradley Rockwell Automation Logix5000 ControlLogix CompactLogix SoftLogix FlexLogix PowerFlex 700S DriveLogix FactoryTalk FactoryTalk AssetCentre RSMACC PanelView RSLinx RSLogix 5000 PLC-5 and TechConnect are trademarks of Rockwell Automation Inc
Trademarks not belonging to Rockwell Automation are property of their respective companies
WARNINGIdentifies 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
IMPORTANT Identifies information that is critical for successful application and understanding of the product
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
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
Summary of Changes
Introduction This revision of this document contains new and updated information To find new and updated information look for change bars as shown next to this paragraph
Updated Information This document contains a new chapter that describes the controller log feature Refer to Controller Logging on page 23
The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
3Publication 1756-RM006E-EN-P - July 2008 3
Summary of Changes
Notes
4 Publication 1756-RM006E-EN-P - July 2008
Table of Contents
Preface Purpose of This Manual 7
Chapter 1Connections Introduction 9
Inhibit a Connection 10Manage a Connection Failure 12
Configure a Major Fault to Occur 14Monitor the Health of a Module 14
Chapter 2Determine Controller Memory Information
Introduction 17Estimate Memory Information Offline 18View Run Time Memory Information 19Write Logic to Get Memory Information 20
Get Memory Information from the Controller 20Choose the Memory Informationt 21Convert INTs to a DINT 22
Chapter 3Controller Logging Introduction 23
Controller Log 23Controller Log Header 24Controller Log Entry 24Entries Captured in the Controller Log 25Controller Log Buffer 26Controller Log Files and the CompactFlash Card 26Writing the Controller Log to the CompactFlash Card 27Controller Logging Counters 30Log File Storage 35Log File Format 36Log File Format 36Creating Custom Log Entries 37Sample Ladder Logic File 38Controller Log Events 39
Chapter 4Access Status Information Introduction 47
Status of SFS When the Project Has an SFC 48Get and Set System Data 48Rockwell Automation Support 54
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Important User InformationSolid 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-11 available from your local Rockwell Automation sales office or online at httpliteraturerockwellautomationcom) 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
Allen-Bradley Rockwell Automation Logix5000 ControlLogix CompactLogix SoftLogix FlexLogix PowerFlex 700S DriveLogix FactoryTalk FactoryTalk AssetCentre RSMACC PanelView RSLinx RSLogix 5000 PLC-5 and TechConnect are trademarks of Rockwell Automation Inc
Trademarks not belonging to Rockwell Automation are property of their respective companies
WARNINGIdentifies 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
IMPORTANT Identifies information that is critical for successful application and understanding of the product
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
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
Summary of Changes
Introduction This revision of this document contains new and updated information To find new and updated information look for change bars as shown next to this paragraph
Updated Information This document contains a new chapter that describes the controller log feature Refer to Controller Logging on page 23
The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
3Publication 1756-RM006E-EN-P - July 2008 3
Summary of Changes
Notes
4 Publication 1756-RM006E-EN-P - July 2008
Table of Contents
Preface Purpose of This Manual 7
Chapter 1Connections Introduction 9
Inhibit a Connection 10Manage a Connection Failure 12
Configure a Major Fault to Occur 14Monitor the Health of a Module 14
Chapter 2Determine Controller Memory Information
Introduction 17Estimate Memory Information Offline 18View Run Time Memory Information 19Write Logic to Get Memory Information 20
Get Memory Information from the Controller 20Choose the Memory Informationt 21Convert INTs to a DINT 22
Chapter 3Controller Logging Introduction 23
Controller Log 23Controller Log Header 24Controller Log Entry 24Entries Captured in the Controller Log 25Controller Log Buffer 26Controller Log Files and the CompactFlash Card 26Writing the Controller Log to the CompactFlash Card 27Controller Logging Counters 30Log File Storage 35Log File Format 36Log File Format 36Creating Custom Log Entries 37Sample Ladder Logic File 38Controller Log Events 39
Chapter 4Access Status Information Introduction 47
Status of SFS When the Project Has an SFC 48Get and Set System Data 48Rockwell Automation Support 54
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Summary of Changes
Introduction This revision of this document contains new and updated information To find new and updated information look for change bars as shown next to this paragraph
Updated Information This document contains a new chapter that describes the controller log feature Refer to Controller Logging on page 23
The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
3Publication 1756-RM006E-EN-P - July 2008 3
Summary of Changes
Notes
4 Publication 1756-RM006E-EN-P - July 2008
Table of Contents
Preface Purpose of This Manual 7
Chapter 1Connections Introduction 9
Inhibit a Connection 10Manage a Connection Failure 12
Configure a Major Fault to Occur 14Monitor the Health of a Module 14
Chapter 2Determine Controller Memory Information
Introduction 17Estimate Memory Information Offline 18View Run Time Memory Information 19Write Logic to Get Memory Information 20
Get Memory Information from the Controller 20Choose the Memory Informationt 21Convert INTs to a DINT 22
Chapter 3Controller Logging Introduction 23
Controller Log 23Controller Log Header 24Controller Log Entry 24Entries Captured in the Controller Log 25Controller Log Buffer 26Controller Log Files and the CompactFlash Card 26Writing the Controller Log to the CompactFlash Card 27Controller Logging Counters 30Log File Storage 35Log File Format 36Log File Format 36Creating Custom Log Entries 37Sample Ladder Logic File 38Controller Log Events 39
Chapter 4Access Status Information Introduction 47
Status of SFS When the Project Has an SFC 48Get and Set System Data 48Rockwell Automation Support 54
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Summary of Changes
Notes
4 Publication 1756-RM006E-EN-P - July 2008
Table of Contents
Preface Purpose of This Manual 7
Chapter 1Connections Introduction 9
Inhibit a Connection 10Manage a Connection Failure 12
Configure a Major Fault to Occur 14Monitor the Health of a Module 14
Chapter 2Determine Controller Memory Information
Introduction 17Estimate Memory Information Offline 18View Run Time Memory Information 19Write Logic to Get Memory Information 20
Get Memory Information from the Controller 20Choose the Memory Informationt 21Convert INTs to a DINT 22
Chapter 3Controller Logging Introduction 23
Controller Log 23Controller Log Header 24Controller Log Entry 24Entries Captured in the Controller Log 25Controller Log Buffer 26Controller Log Files and the CompactFlash Card 26Writing the Controller Log to the CompactFlash Card 27Controller Logging Counters 30Log File Storage 35Log File Format 36Log File Format 36Creating Custom Log Entries 37Sample Ladder Logic File 38Controller Log Events 39
Chapter 4Access Status Information Introduction 47
Status of SFS When the Project Has an SFC 48Get and Set System Data 48Rockwell Automation Support 54
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Table of Contents
Preface Purpose of This Manual 7
Chapter 1Connections Introduction 9
Inhibit a Connection 10Manage a Connection Failure 12
Configure a Major Fault to Occur 14Monitor the Health of a Module 14
Chapter 2Determine Controller Memory Information
Introduction 17Estimate Memory Information Offline 18View Run Time Memory Information 19Write Logic to Get Memory Information 20
Get Memory Information from the Controller 20Choose the Memory Informationt 21Convert INTs to a DINT 22
Chapter 3Controller Logging Introduction 23
Controller Log 23Controller Log Header 24Controller Log Entry 24Entries Captured in the Controller Log 25Controller Log Buffer 26Controller Log Files and the CompactFlash Card 26Writing the Controller Log to the CompactFlash Card 27Controller Logging Counters 30Log File Storage 35Log File Format 36Log File Format 36Creating Custom Log Entries 37Sample Ladder Logic File 38Controller Log Events 39
Chapter 4Access Status Information Introduction 47
Status of SFS When the Project Has an SFC 48Get and Set System Data 48Rockwell Automation Support 54
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Table of Contents
Notes
6 Publication 1756-PM015B-EN-P - July 2008
Preface
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Preface
Purpose of This Manual This manual describes how Logix5000 controllers use connections This manual also describes how to get controller information and status This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers For a complete list of common procedures manuals see the Logix5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Preface
Notes
8 Publication 1756-PM015B-EN-P - July 2008
Chapter 1
Connections
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Chapter 1
Connections
Introduction A Logix5000 controller uses connections for many 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 IO 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
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system These communication types use connections
bull IO modules
bull Produced and consumed tags
bull Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet interval (RPI)
The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module
bull Typically you configure an RPI in milliseconds (ms) The range is 02 ms (200 microseconds) to 750 ms
bull 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 you automatically define the path for a connection when you add the devices to the IO Configuration folder of the controller
IO Configuration
[0] 1756-CNBx Local_CNB
2 [0] 1756-CNBx chassis_b
[1] 1756-L55x peer_controller
minus
minus
minus
9Publication 1756-PM015B-EN-P - July 2008 9
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
1 Connections
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 you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with the modules
When you configure an IO module it defaults to being not inhibited You can change an individual modulersquos properties to inhibit a module
When you inhibit a communication bridge module such as a 1756-CNB or 1756-DHRIO module the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module Inhibiting a communication bridge module lets you disable an entire branch of the IO network
ATTENTION Inhibiting a module breaks the connection to the module and prevents communication of IO data
Inhibit communication with the module
If you want to Then
Communicate with the module Do not inhibit the module
Prevent communication with the module Inhibit the module
10 Publication 1756-PM015B-EN-P - July 2008
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Connections 1
When you inhibit the module the controller organizer displays a yellow attention symbol over the module
Follow these steps to inhibit or unhibit a module from logic
1 Use a Get System Value (GSV) instruction to read the Mode attribute for the module
2 Set or clear bit 2
If you are And you And Then
Offline The inhibit status is stored in the project When you download the project the module is still inhibited
Online Inhibit a module while you are connected to the module
The connection to the module is closed The modulesrsquo outputs go to the last configured Program mode
Inhibit a module but a connection to the module was not established (perhaps due to an error condition or fault)
The module is inhibited The module status information changes to indicate that the module is inhibited and not faulted
Uninhibit a module (clear the check box)
No fault occurs
A connection is made to the module and the module is dynamically reconfigured (if the controller is the owner controller) with the configuration you created for that module If the controller is configured for listen-only it cannot reconfigure the module
Fault occurs A connection is not made to the module The module status information changes to indicate the fault condition
If you want to Then
Inhibit the module Set bit 2
Uninhibit the module Clear bit 2
Publication 1756-PM015B-EN-P - July 2008 11
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
1 Connections
3 Use a Set System Value (SSV) instruction to write the Mode attribute back to the module
Manage a Connection Failure
EXAMPLE Inhibit a Connection
If Module_1_Inhibit = 1 then inhibit the operation of the IO module named Module_1
1 The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module
2 The OTE instruction sets bit 2 of Module_1_Mode = 1 This means inhibit the connection
3 The SSV instruction sets the Mode attribute for the module = Module_1_Mode
ATTENTION Outputs respond to the last non-faulted state of the controlling inputs To avoid potential injury and damage to machinery make sure this does not create unsafe operation Configure critical IO modules to generate a controller major fault when they lose their connections to the controller or monitor the status of IO modules
12 Publication 1756-PM015B-EN-P - July 2008
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Connections 1
If the controller loses communication with a module data from that device does not update When this occurs the logic makes decisions on data that may or may not be correct
If communication with a device in the IO configuration of the controller does not occur for 100 ms the communication times out If this occurs you have these options
EXAMPLE Loss of Communication
Controller B requires data from controller A If communication fails between the controllers then controller B continues to act on the last data that it received from controller A
A
B
Communication Failure
41031
If you want the controller to Then
Fault (major fault) Configure a Major Fault to Occur
Continue operating Monitor the Health of a Module
Publication 1756-PM015B-EN-P - July 2008 13
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
1 Connections
Configure a Major Fault to Occur
You can configure modules to generate a major fault in the controller if they lose their connection with the controller This interrupts the execution of logic and executes the Controller Fault Handler If the Controller Fault Handler does not clear the fault then the controller shuts down
Monitor the Health of a Module
If you do not configure the major fault to occur you should monitor the module status If a module loses its connection to the controller outputs go to their configured faulted state The controller and other IO modules continue to operate based on old data from the module
If communication with a module times out the controller produces these warnings
bull The IO status indicator on the front of the controller flashes green
bull A shows over the IO configuration folder and over the device that has timed out
bull A module fault code is produced which you can access throughndash Module Properties window for the modulendash GSV instruction
If the connection times out produce a majorfault in the controller
If the connection times out continue operation without invoking a major fault on the controller
14 Publication 1756-PM015B-EN-P - July 2008
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Connections 1
To monitor the health of your connections use a Get System Value (GSV) instruction to monitor the MODULE object for either the controller or a specific module
If you want to Get this attribute Data Type Description
Determine if communication has timed out with any device
LEDStatus INT
For efficiency use a DINT as the destination data type
Specifies the current state of the IO status indicator on the front of the controller
You do not enter an instance name with this attribute This attribute applies to the entire collection of modules
Value Meaning
0 Status Indicator off No MODULE objects are configured for the controller (there are no modules in the IO 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
Determine if communication has timed out with a specific device
FaultCode INT
For efficiency use a DINT as the destination data type
A number that identifies a module fault if one occurs
In the Instance Name choose the device whose connection you want to monitor Make sure to assign a name to the device in the IO Configuration folder of the project
Publication 1756-PM015B-EN-P - July 2008 15
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
1 Connections
EXAMPLE Monitor the Health of a Module
The GSV instruction continuously sets I_O_LED_Status (DINT tag) = status of the IO LED of the controller
If I_O_LED_Status = 2 then communication has timed out (faulted) with at least one module The GSV instruction sets Module_3_Fault_Code = fault code for Module_3
If Module_3_Fault_Code is NOT equal to 0 then communication has timed out (faulted) with Module_3 The OTE instruction sets Module_3_Faulted = 1
16 Publication 1756-PM015B-EN-P - July 2008
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Chapter 2
Determine Controller Memory Information
Introduction Depending on your type of controller the memory of the controller may be divided into several areas
If you have this controller Then it stores this In this memory
ControlLogix IO tags IO memory
Produced tags
Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPCDDE) tags that use RSLinx software(1)
Tags other than IO produced or consumed tags Data and logic memory(2)
Logic routines
Communication with polled (OPCDDE) tags that use RSLinx software(1)
bull CompactLogix
bull FlexLogix
bull DriveLogix
bull SoftLogix5800
These controllers do not divide their memory They store all elements in One common memory area
(1) To communicate with polled tags the controller uses both IO data and logic memory
(2) 1756-L55M16 controllers have an additional memory section for logic
17Publication 1756-PM015B-EN-P - July 2008 17
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
2 Determine Controller Memory Information
Estimate Memory Information Offline
To estimate how much controller memory your project requires use the Memory tab of the controller properties dialog box For each of the memory areas of your controller it lets you estimate number of bytes of
bull free (unused) memorybull used memorybull largest free contiguous block of memory
1 Click the controller properties button2 Click the Memory tab
3 For controllers with different memory options choose the memory size (for example M12)
5 Estimate the amount of controller memory
4 View the memory information since the last estimate
18
Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Determine Controller Memory Information 2
View Run Time Memory Information
When online with a controller the Memory tab shows the actual memory usage of the controller While the controller is running it uses additional memory for communication The amount it needs varies depending on the state of the communication
The Memory tab of the controller includes a Max Used entry for each type of memory The Max Used values show the peak of memory usage as communication occur
1 Click the controller properties button2 Click the Memory tab
3 View the memory information
4 To reset the Max Used values click here
Publication 1756-PM015B-EN-P - July 2008
19
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
2 Determine Controller Memory Information
Write Logic to Get Memory Information
To use logic to get memory information for the controllerbull Get Memory Information from the Controllerbull Choose the Memory Informationbull Convert INTs to a DINT
Get Memory Information from the Controller
To get memory information from the controller execute a Message (MSG) instruction that is configured as follows
On this tab For this item Type or select Which means
Configuration Message Type CIP Generic Execute a Control and Information Protocol command
Service Type Custom Create a CIP Generic message that is not available in the pull-down list
Service Code 3 Read specific information about the controller (GetAttributeList service)
Class 72 Get information from the user memory object
Instance 1 This object contains only 1 instance
Attribute 0 Null value
Source Element
source_array of type SINT[12]
In this element Enter Which means
source_array[0] 5 Get 5 attributes
source_array[1] 0 Null value
source_array[2] 1 Get free memory
source_array[3] 0 Null value
source_array[4] 2 Get total memory
source_array[5] 0 Null value
source_array[6] 5 Get largest contiguous block of additional free logic memory
source_array[7] 0 Null value
source_array[8] 6 Get largest contiguous block of free IO memory
source_array[9] 0 Null value
source_array[10] 7 Get largest contiguous block of free data and logic memory
source_array[11] 0 Null value
Source Length 12 Write 12 bytes (12 SINTs)
Destination INT_array of type INT[29]
Communication Path 1 slot_number_of_controller
20 Publication 1756-PM015B-EN-P - July 2008
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Determine Controller Memory Information 2
Choose the Memory Information
The MSG instruction returns the following information to INT_array (destination tag of the MSG)
IMPORTANT The controller returns the values in number of 32-bit words To see a value in bytes multiple it by 4
If your controller does not divide its memory then the values show up as IO memory
For a 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
If you want the Then copy these array elements Description
Amount of free IO memory (32-bit words) INT_array[3] Lower 16 bits of the 32 bit value
INT_array[4] Upper 16 bits of the 32 bit value
Amount of free data and logic memory (32-bit words) INT_array[5] Lower 16 bits of the 32 bit value
INT_array[6] Upper 16 bits of the 32 bit value
1756-L55M16 controllers onlymdashamount of additional free logic memory (32-bit words)
INT_array[7] Lower 16 bits of the 32 bit value
INT_array[8] Upper 16 bits of the 32 bit value
Total size of IO memory (32-bit words) INT_array[11] Lower 16 bits of the 32 bit value
INT_array[12] Upper 16 bits of the 32 bit value
Total size of data and logic memory (32-bit words) INT_array[13] Lower 16 bits of the 32 bit value
Largest contiguous block of free IO memory (32-bit words) INT_array[23] Lower 16 bits of the 32 bit value
INT_array[24] Upper 16 bits of the 32 bit value
Largest contiguous block of free data and logic memory (32-bit words)
INT_array[27] Lower 16 bits of the 32 bit value
INT_array[28] Upper 16 bits of the 32 bit value
Publication 1756-PM015B-EN-P - July 2008 21
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
2 Determine Controller Memory Information
Convert INTs to a DINT
The MSG instruction returns each memory value as two separate INTsbull The first INT represents the lower 16 bits of the valuebull The second INT represents the upper 16 bits of the value
To convert the separate INTs into one usable value use a Copy (COP) instruction
In the following example the COP instruction produces the 32-bit value that represents the amount of free IO memory in 32-bit words
In this operand Specify Which means
Source First INT of the 2 element pair (lower 16 bits)
Start with the lower 16 bits
Destination DINT tag in which to store the 32-bit value Copy the value to the DINT tag
Length 1 Copy 1 times the number of bytes in the Destination data type In this case the instruction copies 4 bytes (32 bits) which combines the lower and upper 16 bits into one 32-bit value
EXAMPLE Convert INTs to a DINT
bull Elements 3 of INT_array is the lower 16 bits of the amount of free IO memory Element 4 is the upper 16 bits
bull Memory_IO_Free is a DINT tag (32 bits) in which to store the value for the amount of free IO memory
bull To copy all 32 bits specify a Length of 1 This tells the instruction to copy 1 times the size of the Destination (32 bits) This copies both element 3 (16 bits) and element 4 (16 bits) and places the 32-bit result in Memory_IO_Free
22 Publication 1756-PM015B-EN-P - July 2008
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Chapter 3
Controller Logging
Introduction The controller logging feature provides a way to detect and log changes made to ControlLogix 1756-L6x controllers without adding any auditing software With controller logging the 1756-L6x controllers
bull detect changes and create logs entries containing information about the changes
bull store the log entries to the CompactFlash card for later reviewbull provide programmatic access to log entry counters to provide change
detection information remotely
Controller logging is not integrated with FactoryTalk AssetCentre or RSMACC utilities
Controller Log A controller log is a record of RSLogix 5000 programming software and key switch interactions that have occurred with the controller Up to 100 log entries are buffered within the controllers memory The controller can save these buffered entries to the CompactFlash card by using a message instruction Additionally the controller can be configured to automatically write buffered entries to the CompactFlash card after 80 entries have accumulated
Topic Page
Controller Log 23
Controller Log Header 24
Controller Log Entry 24
Entries Captured in the Controller Log 25
Controller Log Buffer 26
Controller Log Files and the CompactFlash Card 26
Writing the Controller Log to the CompactFlash Card 27
Controller Logging Counters 30
Log File Storage 35
Log File Format 36
Creating Custom Log Entries 37
Sample Ladder Logic File 38
Controller Log Events 39
23Publication 1756-PM015B-EN-P - July 2008 23
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Example Controller Log File
Controller Log Header
When the controller creates a log file on the CompactFlash card it includes some header information This header information includes the
bull date the log file was createdbull controller model numberbull controller serial numberbull version of firmware running on the controller
Controller Log Entry
Each entry in the log can include the following information
bull Record Numberbull Time of Occurrence (UTC - 24 hour clock)bull Entry Descriptionbull Windows User Namebull Workstation Namebull FactoryTalk User ID (if available)bull Extended Information
Record Number Time Event Description User Name Workstation Name
FactoryTalk ID Extended Information
1 02-Feb 120000 RSLogix 5000 Download
IBSmith WS1250T Engineer Project LoaderCLX
2 03-Feb 040512 Forces Enabled Jones USMAYLT FTJones
3 06-Feb 032203 Online edits modified controller program
JohnDoe Laptop FTJDoe
4 06-Feb 033034 Firmware Update Attempted
JohnDoe Laptop FTJDoe Old Rev 1700 New Rev 1801
24 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Example Excel File of a Controller Log
Entries Captured in the Controller Log
Below is a list of entries that are detected and logged These events are described in more detail in Controller Log Events on page 39
bull Project downloadedbull Loaded from removable mediabull Stored to removable mediabull Online edits tested or assembledbull Partial import online completedbull IO forces enabled disabled removed or modifiedbull SFC forces enabled disabled removed or modifiedbull Firmware updatebull Mode changebull Major faultbull Major fault clearedbull Program properties modifiedbull Task properties modifiedbull Controller timeslice modifiedbull Removable media inserted or removedbull Safety signature created or deletedbull Safety locked or unlockedbull Custom entry User defined logic to create a log entry with user defined
entry description and extended information
Publication 1756-PM015B-EN-P - July 2008 25
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Controller Log Buffer
The controller keeps up to 100 log entries buffered in its internal memory If so configured the controller can write the buffered entries to the CompactFlash card when its internal buffer becomes 80 full Additionally the controller can be commanded to write the buffered entries to the CompactFlash card with a message instruction This procedure is detailed below Once a log entry is written to the CompactFlash card it is removed from the buffer
If the CompactFlash card is not present is full or if the controller is not configured to automatically write buffered entries to the CompactFlash card and the internal buffer becomes full entries will continue to be saved in the buffer in a circular fashion As new entries are stored the oldest entries will be discarded
Controller Log Files and the CompactFlash Card
When written to the CompactFlash card controller logs are stored in plain text files in the Tab Separated Value (TSV) format Each time the controller writes 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 will not attempt to write log entries to a full CompactFlash card In the event that the CompactFlash card becomes full the system will behave as if the CompactFlash card is not present
As controller log files are stored in plain text files in the TSV format no special tools are required to read them They can be opened in any text editor or in a spreadsheet application such as Microsoft Excel File storage is further described below
26 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Writing the Controller Log to the CompactFlash Card
The controller log can be written to the CompactFlash card either automatically or on demand
Automatic Save
When the controllers internal log entry buffer becomes 80 full it can automatically write the buffered entries to the CompactFlash card Additionally buffered entries can be automatically written before a firmware update This is configured by sending a message instruction to the controller using a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Setrdquo Sending a value of 0 will turn off automatic writes and sending a value of 1 will turn 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 below
Automatic Save ldquoSetrdquo Ladder Instruction
Automatic Save ldquoSetrdquo Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 27
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
The current state of the automatic write setting can be retrieved by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Automatic Write Getrdquo A rung of ladder logic that gets this value and the configuration of the message instruction are shown below
Automatic Save ldquoGetrdquo Ladder Instruction
Automatic Save ldquoGetrdquo Configuration Dialog Box
28 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Save On Demand
The controller can be commanded to write buffered entries to the CompactFlash card by using a message instruction with a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Write To Mediardquo
A rung of ladder logic that sends this message and the configuration of the message instruction are shown below
Write Buffered Entries to the CompactFlash Card Ladder Instruction
Write Buffered Entries to the CompactFlash Card Configuration Dialog Box
Publication 1756-PM015B-EN-P - July 2008 29
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Controller Logging Counters
Three counters provide real time statistics about modifications to the controller
Total Entry Count
Total Entry Count is the number of controller entries that have been added since the last firmware update This counter will increment after any entry is added to the log and it is written to the log in the Record Number field Using a Set System Value (SSV) instruction it can be set 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
Total Entry Count by Using a Get System Value (GSV) Instruction
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware update
GSVSSV
Unsaved Entry Count Number of entries in controller RAM not yet written to the CompactFlash card
GSV
Modify Execution Count Count that specifically tracks modifications that can change behavior of a running controller A subset of entries increment this count
GSVSSV
30 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
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
Set the Total Entry Count to a Known Value 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 to 100 the maximum number of entries that the controller can buffer
This rung of ladder logic shows how to retrieve the Unsaved Entry Count by using a Get System Value (GSV) instruction
Retrieve the Unsaved Entry Count Using a Get System Value Instruction
Execution Modification Count
The Execution Modification Count tracks the number of changes that occur that can change the behavior of a running controller This counter can be configured to include or exclude force changes
Publication 1756-PM015B-EN-P - July 2008 31
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
The events that will cause the Execution Modification Count to increment include the following
bull Online edits tested or assembledbull Forces enabled or disabled (if so configured)bull Program properties modifiedbull Task properties modifiedbull Controller timeslice modified
This counter can be set to a known value by using an SSV instruction
This rung of ladder logic shows how to retrieve the Execution Modification Count by using a GSV instruction
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
Set the Execution Modification Count to a Known Value
A message instruction of message type ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Setrdquo is used to configure whether the Execution Modification Count includes forces If it is sent a value of 1 forces
32 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
will be included in the counter If it is sent a value of 0 forces will not be included
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Set the Execution Count Configure Mask Instruction
Set the Execution Count Configure Mask Dialog Box
The Source Element should be of data type DINT
Publication 1756-PM015B-EN-P - July 2008 33
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
A message instruction is also used to retrieve the current value of this configuration This message uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Config Execution Getrdquo
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown
Get the Execution Count Configure Mask Instruction
Get the Execution Count Configure Mask Dialog Box
The Destination tag should be of type DINT
34 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Log File Storage
When a log file is written to the CompactFlash card it will be stored at ldquoLogixXXXXXXXXLogsVYY_ZZrdquo where XXXXXXX is the eight digit serial number of the controller and YY_ZZ is the version number of the firmware (major_minor revision)
Log File Location
The file will be called ControllerLog_yyytxt where yyy is a sequential number from 000hellip999 The log file will be appended to until it reaches a size greater than 1 MB At that point the next write of the controller log causes a new file to be created with the next sequence number
Once there are 1000 files larger than 1 MB no more logs will be created The controller will however search for the file name with the smallest possible sequence number that it can create or write to For example if a user deletes files 001hellip100 but leaves the rest the controller will start 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 will write 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 Backuptxt The backup is overwritten every time a log file is opened for writing
Publication 1756-PM015B-EN-P - July 2008 35
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Users are responsible for periodically clearing space on the card for new log files The controller does not delete any files off of the card to create more space for new log files
Log File Format
The following table lists the information that is contained in the controller log file
Log File Format
The log file is formatted in UTF-16 and has a file extension of txt Double- clicking the file will open it in Notepad on most systems However since it is formatted as Tab Separated Values (TSV) it can also be opened in a spreadsheet application like Microsoft Excel
The following screen is an example of the log file viewed in Notepad
Controller Log File Viewed in Notepad
The following screen is an example of the log file viewed in Excel
Controller Log File Viewed in Excel
Content Description Format
Time The controllers GMT time MMM-DD-YY HHMMSS24 hour time
Entry Entry Description - Defined in Entry List section
User Name The users login ID Windows domain name with display name if available
Workstation Name The users computer name Computer Name
FactoryTalk ID The users FactoryTalk login ID Alphanumeric characters
Extended Information
Entry specific information Defined in Entry List section
36 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Creating Custom Log Entries
Custom entries can be added to the controller log by using a message instruction The message instruction uses a message type of ldquoCIP Genericrdquo and a service type of ldquoController Log Add Entryrdquo
The source element of this message should be a tag of a user-defined data type The user-defined data type should contain two string members The first string will be put in the log entrys Description field The second string will be put in the log entrys Extended Information field
The rung of ladder logic below shows how to send the message instruction The configuration dialog box of the message instruction is also shown as is the definition of the user-defined data type used for the source element
Send the Message Instruction
Controller Log Add Entry Dialog Box
Publication 1756-PM015B-EN-P - July 2008 37
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Example Data Type Dialog Box
Sample Ladder Logic File
In RSLogix 5000 software there is a controller logging sample ladder file If you installed the sample files during the installation the file ControllerLogServicesACD will be located at the following location
38 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Controller Log Events
This table describes the events that the controller stores in the controller log
Entry Information Logged
Project download bull Time Stamp
bull Entry Description Project download
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media
bull Time Stamp
bull Entry Description Project load
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Load from removable media auto-initiated
bull Time Stamp
bull Entry Description Project auto load
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Project
Store to removable media
bull Time Stamp
bull Entry Description Project store
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Project
Online edits tested or assembled
bull Time Stamp
bull Entry Description Online edits modified controller program
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
bull Edits logged are
- Test Program Edits- UnTest Program Edits- Assemble Program Edits- Accept Program Edits- Accept Pending Rung Edits
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
SFC forces disabled bull Time Stamp
bull Entry Description SFC forces disabled
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
SFC forces removed bull Time Stamp
bull Entry Description SFC forces removed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
SFC forces modified bull Time Stamp
bull Entry Description SFC element force value changed
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Routine
Firmware update from workstation
bull Time Stamp
bull Entry Description Firmware update attempted
bull UserName None
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Firmware update from removable media
bull Time Stamp
bull Entry Description Firmware update from removable media attempted
bull UserName Local
bull Workstation None
bull FactoryTalk Login Id None
bull Extended Information Old revision ltmajorltminorgt New revision ltmajorltminorgtWhere the major and minor revision numbers are each two digits
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 41
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Mode change started bull Mode change started Time Stamp
bull Entry Description Remote mode change
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Mode change started via key switch
bull Time Stamp
bull Entry Description Keyswitch mode change
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Old mode ltmodegt New mode ltmodegt
bull Possible modes
- Run- Remote Run- Test- Program- Remote Program
Major fault bull Time Stamp
bull Entry Description A major fault occurred
bull UserName None
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information Fault type lttype numbergt Fault code ltcode numbergt
Major faults cleared bull Time Stamp
bull Entry Description All major faults cleared
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Entry Information Logged
42 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Major faults cleared through key switch
bull Time Stamp
bull Entry Description All major faults cleared
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Program properties modified
bull Time Stamp
bull Entry Description Program properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Program
bull Property changes logged
- Inhibit checkbox- Main routine changed- Fault routine changed
Task properties modified
bull Time Stamp
bull Entry Description Task properties modified
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Task
bull Task property changes logged
- Type changed- Inhibit checkbox- Disable Automatic Output Processing to Reduce Task
Overhead checkbox- Priority value- Period Value- Execute if no Event occurs within X ms check box- Trigger changed- Trigger Tag changed- Schedule changedUnscheduled operation
- System Overhead Time Slice- During unused System Overhead Time Slice radio buttons
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 43
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Removable media removed
bull Time Stamp
bull Entry Description Removable media removed
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Removable media inserted
bull Time Stamp
bull Entry Description Removable media inserted
bull UserName Local
bull Workstation Name None
bull FactoryTalk Login Id None
bull Extended Information None
Safety signature create
bull Time Stamp
bull Entry Description Safety signature create
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Safety signature delete
bull Time Stamp
bull Entry Description Safety signature delete
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information Signature number 0xYYYYYYYY (hex format)
Entry Information Logged
44 Publication 1756-PM015B-EN-P - July 2008
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Controller Logging 3
Safety lock bull Time Stamp
bull Entry Description Safety lock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Safety unlocked bull Time Stamp
bull Entry Description Safety unlock
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information None
Custom entry bull Time Stamp
bull Entry Description ltUser supplied stringgt maximum 40 characters
bull UserName
bull Workstation Name
bull FactoryTalk Login Id
bull Extended Information ltUser supplied infogt maximum 82 characters
Entry Information Logged
Publication 1756-PM015B-EN-P - July 2008 45
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
3 Controller Logging
Notes
46 Publication 1756-PM015B-EN-P - July 2008
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Chapter 4
Access Status Information
Introduction The controller supports status keywords you can use in your logic to monitor specific events
bull The status keywords are not case sensitivebull Because the status flags can change so quickly RSLogix 5000 software
does not display the status of the flags For example even when a status flag is set an instruction that references that flag is not highlighted
bull You cannot define a tag alias to a keyword
You can use these key words
To determine if Use
The value you are storing cannot fit into the destination because it is either
bull greater than the maximum value for the destination
bull less than the minimum value for the destination
Important Each time SV goes from cleared to set it generates a minor fault (type 4 code 4)
S V
The instructionrsquos destination value is 0 SZ
The instructionrsquos destination value is negative SN
An arithmetic operation causes a carry or borrow that tries to use bitsthat are outside of the data type
For example
bull adding 3 + 9 causes a carry of 1
bull subtracting 25 - 18 causes a borrow of 10
SC
This is the first normal scan of the routines in the current program SFS
At least one minor fault has been generated
bull The controller sets this bit when a minor fault occurs due to program execution
bull The controller does not set this bit for minor faults that are not related to program execution such as battery low
SMINOR
47Publication 1756-PM015B-EN-P - July 2008 47
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
4 Access Status Information
Status of SFS When the Project Has an SFC
The state of SFS depends on the status of the SFC
bull If you use SFS in an action of a sequential function chart (SFC) SFS is set (on) for one scan each time the step goes active SFS = step_nameFS
bull If the SFC calls a routine SFS is set (on) for one scan each time the step that calls the routine goes active SFS = step_nameFS
If the SFC does not call a routine SFS is set (on) for the first scan of the task
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 GSVSSV instructions to get and set controller system data that is stored in objects
bull The GSV instruction retrieves the specified information and places it in the destination
bull The SSV instruction sets the specified attribute with data from the source
Follow these steps to get or set a system value
1 Open the RSLogix 5000 project
2 From the Help menu choose Contents
3 Click the Index tab
4 Type GSVSSV objects and click Display
EXAMPLE SFC Calls a Ladder Diagram
Suppose several steps in an SFC call the same Ladder diagram routine And suppose the Ladder diagram uses SFS Each time one of those steps goes active SFS turns on for one scan of the Ladder diagram
EXAMPLE Several Tasks but No SFC
Suppose you have two tasks that use Ladder diagrams When the first task runs for the first time SFS turns on for one scan After that SFS stays off for that task When the other task runs for the first time SFS turns on for one scan in that task SFS stays off in the first task that ran
ATTENTION Use the SSV instruction carefully Making changes to objects can cause unexpected controller operation or injury to personnel
48 Publication 1756-PM015B-EN-P - July 2008
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Access Status Information 4
5 Select the object
6 In the list of attributes for the object identify the attribute that you want to access
7 Create a tag for the value of the attribute
8 In the Ladder Logic routine enter the appropriate instruction
To get or set Click
Axis of a servo module AXIS
System overhead timeslice CONTROLLER
Physical hardware of a controller CONTROLLERDEVICE
Coordinated system time for the devices in one chassis CST
DF1 communication driver for the serial port DF1
Fault history for a controller FAULTLOG
Attributes of a message instruction MESSAGE
Status faults and mode of a module MODULE
Group of axes MOTIONGROUP
Fault information or scan time for a program PROGRAM
Instance number of a routine ROUTINE
Configuration of the serial port SERIALPORT
Properties or elapsed time of a task TASK
wall clock time of a controller WALLCLOCKTIME
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 DINT[7])
A Create a user-defined data type that matches the organization of data that is used by the attribute
B Create a tag for the attribute and use the data type from step A
To Enter this instruction
Get the value of an attribute GSV
Set the value of an attribute SSV
Publication 1756-PM015B-EN-P - July 2008 49
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
4 Access Status Information
9 Assign the required operands to the instruction
This examples gets the current date and time
For more information see the Logix5000 Controllers General Instruction Set Reference Manual publication 1756-RM003
For this operand Select
Class name Name of the object
Instance name Name of the specific object (for example name of the required IO module task message)
bull Not all objects require this entry
bull To specify the current task program or routine select THIS
Attribute name Name of the attribute
Dest (GSV) Tag that will store the retrieved value
If the tag is a user-defined data type or an array select the first member or element
Source (SSV) Tag that stores the value to be set
If the tag is a user-defined data type or an array select the first member or element
EXAMPLE Get a System Value
At the first scan 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
42370
50 Publication 1756-PM015B-EN-P - July 2008
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
How Are We DoingYour comments on our technical publications will help us serve you better in the futureThank you for taking the time to provide us feedbackYou can complete this form and mail (or fax) it back to us or email us at RADocumentCommentsrarockwellcom
Please complete the sections below Where applicable rank the feature (1=needs improvement 2=satisfactory and 3=outstanding)Pub TitleType Logix5000 Controllers Controller Information and Status
Cat No 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix 1794 FlexLogix PowerFlex 700S with DriveLogix
Pub No 1756-PM015B-EN-P Pub Date July 2008 Part No
Overall Usefulness 1 2 3 How can we make this publication more useful for you
Completeness(all necessary information
is provided)
1 2 3 Can we add more information to help you
procedurestep illustration feature
example guideline other
explanation definition
Technical Accuracy(all provided information
is correct)
1 2 3 Can we be more accurate
text illustration
Clarity(all provided information is
easy to understand)
1 2 3 How can we make things clearer
Other Comments You can add additional comments on the back of this form
Your Name
Your TitleFunction Would you like us to contact you regarding your comments
LocationPhone ___No there is no need to contact me
___Yes please call me
___Yes please email me at _______________________
___Yes please contact me via _____________________
Return this form to Rockwell Automation Technical Communications 1 Allen-Bradley Dr Mayfield Hts OH 44124-9705
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Other Comments
PLEASE FOLD HERE
NO POSTAGE NECESSARY IF MAILED
IN THE UNITED STATES
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEA
SE R
EMOV
E
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Publication 1756-PM015B-EN-P - July 2008 54Supersedes Publication 1756-PM015A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom 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 httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running
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 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for the return procedure
1756-PM015B-EN-P
Important User Information
Summary of Changes
Introduction
Updated Information
Table of Contents
Preface
Purpose of This Manual
1 - Connections
Introduction
Inhibit a Connection
Manage a Connection Failure
Configure a Major Fault to Occur
Monitor the Health of a Module
2 - Determine Controller Memory Information
Introduction
Estimate Memory Information Offline
View Run Time Memory Information
Write Logic to Get Memory Information
Get Memory Information from the Controller
Choose the Memory Information
Convert INTs to a DINT
3 - Controller Logging
Introduction
Controller Log
Controller Log Header
Controller Log Entry
Entries Captured in the Controller Log
Controller Log Buffer
Controller Log Files and the CompactFlash Card
Writing the Controller Log to the CompactFlash Card
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool
100 Gloss Text
100 Text
10pt C1S Cover
10pt C2S Cover
10pt C2S Text
10pt Text Stock
110 White Index
12pt C1S Cover
20 White Opaque Bond
50 Colored Offset
50 White Offset
50 White Opaque
60 Cover Stock
60 White Offset
80 Gloss Cover
80 Gloss Text
8pt C1S White
90 White Index
CoverText Ink
Black
Black + 1 PMS color
Type in PMS color
Black + 2 PMS colors
Type in PMS colors
4 color
4 color over black
4 color + 1 PMS color
Type in PMS color
4 color over black + 1 PMS color
Type in PMS color
4 color + 2 PMS colors
Type in PMS colors
4 color + aqueous
4 color + varnish
dPrint
ContentComp
Split Shipment Indicator Flag
WCSS Item Number
Customer Item Number
Item Description
Producing Plant
Job Number
Replenishing Plant
Plant Code
Product Code
PackagingOrdering UOM
Qty per PackagingOrdering UOM
List Price Per Ea
Transfer Cost per Ea
Sell Price per Ea
Standard Cost (per Ea)
Min Order Qty (in eaches)
Multiple Order Qty (in Eaches
Chargeback Price
Item Reference 1
Item Reference 2
Revision Field
Max Order Qty (in eaches)
Sequentially Numbered Item
Sequentially Numbered Item - Details
Priced for Digital or Offset
Content File Location
Item Category Form (F) Book (B)
Item Subtype
Orientation
Sides Printed
CSSJLS Stock Componet
Paper Size Width
Paper Size Length
No of Forms to a Sheet
Page Qty
Sheets Qty
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
of Tabs
Binder Size
Binder Color
Binder Ring Type
Binder Transparency (clearview or matt)
Thermal Tape Color
Trim Size Width
Trim Size Length
Stitching Location
Drilling Size
Drilling Location
Glue Location
Pad
Fold Type
Fold At
Poly
Box
Comments
Cross Reference Item Number 1
Publication Number
Publication Title
PackagingOrdering Unit Of Measure
Qty per PackagingOrdering Unit of Measure
Min Order Qty
Multiple Order Qty
Business Group
Cost Center
Revision Date
Max Order Qty
Black amp Whiteor Color
Item CategoryForm (F) or Book (B)
BindingStitching
Orientation
Sides Printed
Printing Paper Size Width
Printing Paper Size Length
Number of Forms to a Sheet
Page Count of Publication
Number of Sheets Required to Print
CSSJLS Production Stock
Paper Stock Type
Paper Stock Weight
Paper Stock Color
Stack Offset
Tab Size
Number of Tabs Needed
Binder Size
Binder Color
Binder Ring Type
Binder Transparency
Thermal Tape Color
Finished Trim Size Width
Finished Trim Size Length
Stitching Location
Drill Hole Size
Number and Location of Drill Holes
Glue Location
Number of Pages per Pad
Fold Type
Fold At
Number of Pieces per Poly wrap
Number of Pieces per Box
Comments
Part Number
Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup
The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8
Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items
Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number
30 characters maximum
Cannot use quote symbol that is----
Required Which plantPrint Center will produce this item
Required To be provided from the producing plant for JIT su
Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant
Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below)
Required Enter one of the applicable product
Method of packaging for publication shipmentClick here for explanation of each value in the pull-down
Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes)
Required Transfer Cost per orderingpackaging unit of measure
Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet
Required Replacement Cost per Packagingordering UOM
Click here for an explanation of this field otherwise type NA
Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM)
IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu
IMPORTANT This information must match the DocMan record
IMPORTANT This information must match the DocMan recordDate on the publication
Click here for explanation of each value in the pull-down menu
Indicate Yes or No Enter Yes if the item is a sequentially numbered item
Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers
Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field
Typically a BookClick here for explanation of each value in the pull-down menu
Click here for explanation of each value in the pull-down
Click here for explanation of each value in the pull-down menu
Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book
IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed
IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed
Click here for explanation of how to determine the information required
Click here for explanation of how to determine the information required
Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item
Click here for explanation of how to determine the information required
The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu
If item uses tabs otherwise NA
If needed otherwise type NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If item used in a binder otherwise NA
If publication is thermal tape bound otherwise NA
Click here to see the available finished trim sizesThe sizes are listed - width x length
Click here to see the available finished trim sizesThe sizes are listed - width x length
If publication is Book [B] and stapled otherwise NA
Click here for a list of possible drill locations
If publication uses padding otherwise NA
If publication is a notepad or message pad otherwise NA
Click here for explanation of each value in the pull-down menu Folding of final document optional
The location(s) of the fold
Click here for explanation of each value in the pull-down menu
Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values
List only if pubication is used in manufacturing otherwise leave blank
1756-PM015B-EN-P
Logix5000 Controllers Controller Information and Status Programming Manual
EA
1
1
Marketing Commercial
CMKMAY IA ControlVisNet - 19021
07012008
5
Black amp White
B
PERFECT
PORTRAIT
HEAD2HEAD
RRD must provide this information
RRD must provide this information
2
54
27
PLAIN
20
White
RRD must provide this information
NA
NA
NA
NA
NA
NA
NA
85
11
NA
516
3LEFT
NA
NA
NA
NA
25
RRD must provide this information
Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF
Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn)
Business Group
The business group that the publication supports Your choice here determines the list you choose from for Cost Center
CorporateBusiness Development
Finance
Human Resources
IT
Logistics
Manufacturing
Marketing Commercial
Marketing Europe
Marketing Other
Operations
Order Services
Other
Process Improvement
Procurement
Quality
Sales
Max Order Quantity
Presale items = 100
Postsale items = 5
NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it
Item Category - Form (F) or Book (B)
Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form
Book (B) = Any publication that contains 3 or more pages
BindingStitching
For a Form (F) use
CARBONLESS
CUTSHEET
ENVELOPE
For a Book (B) use
LOOSE
LOOSE -Loose Leaf
PERFECT
PERFECT - Perfect Bound
PLASTCOIL
PLASTCOIL - Plastic Coil (Coil Bound)
SADDLE
SADDLE - Saddle Stitch
STAPLED1
STAPLED1 -1 position
STAPLED1B
STAPLED1B - bottom 1 position
STAPLED2
STAPLED2 - 2 positions
THERMAL
THERMAL - Thermal bound (Tape bound)
THERMALO
THERMALO - Thermal Bound (Tape bound - offline)
WIRE O
Wire O - Double Wire Bound (offline)
Saddle-Stitch Items
20 sheets max on 20 (text and cover)
19 sheets max on 20 (text) and 24 (cover)
18 sheets max on 24 (text and cover)
All page quantities must be divisible by 4
Tape Bound Items
125 sheets max on 20 no cover
120 sheets max wcover (90 index unless indicated otherwise)
Perfect Bound Items
475 sheets max on 20 no cover
470 sheets max wcover (90 index unless indicated otherwise)
Double Wire Bound Items
40 sheets max on 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Coil Bound Items
290 sheets max of 20 (if adding cover deduct equivalent number of pages to equal cover thickness) (90 index unless indicated otherwise)
Sides Printed
Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page
Simplex = Single-sided printing
Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page
Number of Forms to a Sheet
Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4
Number of Sheets Required to Print
Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of one 85 x 11 sheet of paper that is folded in half the Number of Sheets Required to Print = 1
Paper Stock Type
Description
PLAIN
Bond
ACNTCVR
Accent Cover
BOND3H
Bond (3-hole)
BOOKENV
Booklet Envelope
C1SGLOSS
C1S Gloss Finish
C1SMATTE
C1S Matt Finish
C2SGLOSS
C2S Gloss Finish
C2SMATTE
C2S Matt Finish
CARD
Card Stock
CATLGENV
Catalog Envelope
CATLGENV6
6 Catalog Envelope
COVERCOLOR
Color Cover Copy
CRCKPEEL
Crack N Peel Label
CUSTOM
Custom
CVRFUTURA
Futura Cover
ENV6x9
Standard 6X9 Envelope
ENV9X12
Standard 9X12 Envelope
ETHCERT
Ethicon Certificate
GLOSSCOVER
Gloss Cover
GLOSSTEXT
Gloss Text
HOTSTEXT
Hots Text
INDEX
Index
LABEL80
80 Up Label
MICROPRT
Micro Print
OFFSET
Offset
PART2
2 Part
PART3
3 Part
PART4
4 Part
PART5
5 Part
PART6
6 Part
PERF
12 inch Perfed
PERMMAT
Perm Mat Ad
PRECUTTAB
Pre-Cut Tab
PREPERF
Pre-Perforated
RECYL
Recycled
SE10ENV
10 Standard Envelope
SE10ITENV
10 Inside Tint Envelope
SE9ENV
9 Stanard Envelope
TAG
Tag
TEXT
Text
TEXTCOLOR
Text Color Copy
TEXTFUTURA
Futura Text
TEXTLASER
Text Laser Print
TRANSPRNCY
Transparencies
VELLUM
Vellum
VELLUM3HP
Vellum 3HP
WE10ENV
10 Window Envelope
WE9ENV
9 Windor Envelope
WE9ITENV
9 Inside Tint Window Envelope
Paper Stock Color
Black
Blue
Buff
Canary
Cherry
Clear
Cream
Custom
Goldrenrod
Gray
Green
Ivory
Lavender
Manilla
NCRPinkCanary
NCRWhiteBlue
NCRWhiteBlueCanary
NCRWhiteCanary
NCRWhiteCanaryPink
NCRWhiteCanaryPinkGoldenrod
NCRWhiteGreen
NCRWhiteGoldenrodYellow
NCRWhitePink
NCRWhiteWhite
Opaque
Orange
Orchid
Peach
Pink
Purple
Salmon
Tan
Violet
White
Finished Trim Sizes (listed - width x length)
11 x 17
18 x 24 Poster
24 x 36 Poster
3 x 5
36 x 24 Poster
4 x 6
475 x 7
475 x 775
55 x 85
6 x 4
7 x 9
7385 x 9 (RSI Std)
85 x 11
825 x 10875
825 x 11 (RA product profile std)
8375 x 10875
9 x 12
A4
A5
Other - Custom size listed below
Drilling Locations
1CENTER
1LEFTTOP
1TOPCENTER
2LEFT
2LEFT2TOP
2TOP
2TOP2LEFT
2TOP3LEFT
2TOP5LEFT
2TOP5RIGHT
3BOTTOM
3LEFT
3LEFT2TOP
3LEFT3TOP
3RIGHT
3TOP
3TOP5LEFT
5BOTTOM
5CENTER
5LEFT
5RIGHT
5RIGHT2TOP
5TOP
For TRI fold - select Z or C type
Description
HALF
Half
C
C Fold
DBLEPARLL
Double Parallel
OFFSETZ
Offset Z
SAMPLE
See Sample
SHORT
Short Fold
V
V Fold
Z
Z Fold
Number of Pieces per Poly Wrap
Publication length
Number per Poly Wrap
77 or more pages
1
33 to 76 pages
25
3 to 32 pages
50
1 or 2 pages
100
Comments
CoverText Stock
Spine
100 Gloss Cover
If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Do NOT include that page as part of the publication page count Because the addition of a spine will create an odd page count in the PDF contact a Super User to submit your publication via PDFdirect with an exception tool