Programming Manual Logix5000 Controllers Information and Status Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 Compact GuardLogix, 1768 C
Chapter 1 Connections In some situations, such as when initially commissioning a system, it is useful to disable portions of a contr
Connections Chapter 1 If you are And you And Then Uninhibit a module (clear the check box) No fault occurs A connection is ma
Chapter 1 Connections If the controller loses communication with a module, data from that device does not update. When this occurs,
Connections Chapter 1 Configure a major fault to occur You can configure modules to generate a major fault in the controller if th
Chapter 1 Connections If communication with a module times out, the controller produces the following warnings. • The I/O status in
Connections Chapter 1 Example: This rung checks the status of an I/O connection. The controller checks the entry status of the con
Chapter 2 Determine controller memory information Depending on your type of controller, the memory of the controller may be divided into several area
Chapter 2 Determine controller memory information 2. On the Online toolbar (above the Controller Organizer), click the Controller P
Determine controller memory information Chapter 2 When you are online with a controller, the Memory tab shows the actual memory us
Important user information Read this document and the documents listed in the additional resources section about installation, configuration, and ope
Chapter 2 Determine controller memory information There are several ways to use logic to get memory information. • Get memory infor
Determine controller memory information Chapter 2 Choose the memory information The MSG instruction returns the following informat
Chapter 2 Determine controller memory information Convert INTs to a DINT The MSG instruction returns each memory value as two separa
Chapter 3 Controller logging You use the controller logging feature to detect and log changes made to Logix5000 controllers without adding any auditi
Chapter 3 Controller logging Record Number Time Entry Description User Name Workstation Name FactoryTalk ID Extended Information C
Controller logging Chapter 3 The following example shows controller log entries in a spreadsheet. Controller log files are stored
Chapter 3 Controller logging • Change to constant tag configuration reset • Mode change • Major fault, major fault cleared • Pro
Controller logging Chapter 3 The controller does not attempt to write log entries to a full removable media card. If the removable
Chapter 3 Controller logging You can retrieve the current state of the automatic write setting by using a CIP Generic message type
Controller logging Chapter 3 Save On Demand You can command the controller to write buffered entries to the CompactFlash card by
Summary of changes This manual contains new and updated information. There are a number of minor changes throughout this publication that were made t
Chapter 3 Controller logging Controller logging counters Three counters, listed in the following table, provide real-time statistic
Controller logging Chapter 3 Example: Total Entry Count by using a Get System Value (GSV) ladder instruction The following rung o
Chapter 3 Controller logging Example: Retrieve the Unsaved Entry Count using a Get System Value (GSV) ladder instruction Execution
Controller logging Chapter 3 Example: Retrieve the Execution Modification Count by using a GSV ladder instruction The following r
Chapter 3 Controller logging Example: Controller Log Config Execution Set ladder instruction and configuration dialog box The Sour
Controller logging Chapter 3 Example: Controller Log Config Execution Get ladder instruction and configuration dialog box The De
Chapter 3 Controller logging Log File Location The file is named ControllerLog_yyy.txt, where yyy is a sequential number from 000…9
Controller logging Chapter 3 Log file format The following table lists the information that is contained in the controller log fil
Chapter 3 Controller logging Create custom log entries You can add custom entries to the controller log using a message instruction.
Controller logging Chapter 3 Sample ladder Logic file In the Logix Designer application, there is a controller logging sample lad
Chapter 3 Controller logging Entry Information Logged Store to removable media • Time Stamp • Entry Description: Project store •
Controller logging Chapter 3 Entry Information Logged I/O forces modified • Time Stamp • Entry Description: I/O force value cha
Chapter 3 Controller logging Entry Information Logged Firmware update from removable media • Time Stamp • Entry Description: Firm
Controller logging Chapter 3 Entry Information Logged Major faults cleared • Time Stamp • Entry Description: All major faults c
Chapter 3 Controller logging Entry Information Logged Controller time slice modified • Time Stamp • Entry Description: Controller
Controller logging Chapter 3 Entry Information Logged Safety unlocked • Time Stamp • Entry Description: Safety unlock • UserNa
Chapter 3 Controller logging Entry Information Logged Safety signature delete allowed in Run mode • Time Stamp • Entry Descriptio
Chapter 4 Change detection You can use the controller change detection feature as an additional means of detecting changes made to Logix5000 controll
Chapter 4 Change detection Attribute Name Description Access ChangesToDetect Used to specify which changes are monitored. When a
Change detection Chapter 4 Tip: Rockwell recommends using the DINT[2] data type to avoid limitations when working with LINT data t
Table of contents Studio 5000 Environment ... 7 Additional Resources
Chapter 4 Change detection access data using an MSG instruction, refer to the Logix5000 Controllers Messages Programming Manual, pub
Change detection Chapter 4 Bit number Event description 22 Removable media inserted 23 Safety signature created 24 Safety sign
Chapter 4 Change detection To edit the Changes To Detect field, type a new value. To select the events to monitor for changes from a
Chapter 5 Access status information The controller supports status keywords you can use in your logic to monitor specific events. • The status key
Chapter 5 Access status information The state of S:FS depends on the status of the SFC. • If you use S:FS in an action of a sequent
Access status information Chapter 5 4. In the Type in the keyword to find field, type GSV/SSV objects and click Display. 5. In t
Chapter 5 Access status information To Enter this instruction Get the value of an attribute GSV Set the value of an attribute SSV
A access status information 55 AuditValue 51 B bridge module connection 10 C Change Detection 49 ChangesToDetect 50 communicate other cont
Index O objects data storage 56 P path connection route 9 S status access data 55 memory 17 monitor 56 system data access 56 58 Rockwell
Rockwell Automation support Rockwell Automation provides technical information on the web to assist you in using its products. At http://www.rockwell
Table of Contents Chapter 4 Introduction ... 4
Preface This manual describes how Logix5000 controllers use connections with other devices. This manual also describes status keywords and how to get
Preface These documents contain additional information concerning related Rockwell Automation products. Resource Description Industrial Automation
Chapter 1 Connections A Logix5000 controller uses connections for most, but not all, of its communication with other devices. Term Definition Connec
Comments to this Manuals