CPU Event History

CPU Event History allows viewing of logged Boolean Tag events. The Tag must have an off-to-on transition to be logged. The Event History window displays the 18 most recent events. Events are configured using the Data Logger. The Event History can be logged to a USB drive attached to the CPU and can log as many events as the drive memory allows. See Data Logger.

Accessing CPU Event History

There are three methods of accessing CPU Event History:

Method 1

Select the CPU Event History Icon located on the Monitor Toolbar.

Method 2

Select the CPU Event History menu item from the Tools Menu, located on the Main Menu and shown below.

Method 3

Select CPU Event History from the Monitor & Debug topic of the Application Tools panel.

Once selected, a CPU Event History window will open as shown below.

Setting up CPU Event History

The CPU Event History window provides the following:

Read CPU Event History: Select Read CPU Event History to retrieve the system and user Events History stored in the CPU. When the Event History window is initially opened, a read function is performed. The Event History window will be updated with each selection.

Note: This dialog is only available when Connected to the CPU.

The types of events that may be found in the CPU Event History are listed below (GxxBxxSxx values indicate the Group number, Base number, and Slot number of the CPU)

Event Type	Explanation of Event
System Started	CPU started
System Restart	CPU automatically restarted due to unrecoverable internal error
RUN switch	System entered RUN mode due to RUN/STOP switch set to RUN
RUN GxxBxxSxx xxx.xxx.xxx.xxx	System entered RUN mode due to programming software at stated IP address attached to specified module
RUN GxxBxxSxx USB	System entered RUN mode due to programming software connected via USB attached to specified module
STOP switch	System entered STOP mode due to RUN/STOP switch set to STOP
STOP GxxBxxSxx xxx.xxx.xxx.xxx	System entered STOP mode due to programming software at stated IP address attached to specified module
STOP GxxBxxSxx USB	System entered STOP mode due to programming software connected via USB attached to specified module
STOP user program	System entered STOP mode due to STOP PROGRAM instruction in user program
COMM LOST GxxBxxSxx xxx.xxx.xxx.xxx	Connection with programming software disconnected due to loss of communication
COMM LOST GxxBxxSxx USB	Connection with programming software disconnected due to loss of communication
RESET GxxBxxSxx xxx.xxx.xxx.xxx	CPU reset by programming software at stated IP address attached to specified module
RESET GxxBxxSxx USB	CPU reset by programming software connected via USB attached to specified module
NEW PROJ GxxBxxSxx xxx.xxx.xxx.xxx	New project loaded from programming software at stated IP address attached to specified module
NEW PROJ GxxBxxSxx USB	New project loaded from programming software connected via USB attached to specified module
NEW PROJ UIM	New project loaded from USB storage device
EXTRACT GxxBxxSxx xxx.xxx.xxx.xxx	Project extracted by programming software at stated IP address attached to specified module
EXTRACT GxxBxxSxx USB	Project extracted by programming software connected via USB attached to specified module
EXTRACT UIM	Project copied to USB storage device
CLOCK SET	Date/Time has been changed

The types of events that may be found in the CPU Event History are listed below (GxxBxxSxx values indicate the Group number, Base number, and Slot number of the CPU).