Introducing the CPU Status Page

The BMEH584040(S) and BMEH586040(S) Hot Standby CPUs include a Rack Viewer web page. Use this page to view CPU information, including:

  • LEDs status

  • processor identification

  • application signature identification

  • select application configuration settings

Access this page from the Diagnostics tab (System > Rack Viewer).

This example of a Rack Viewer page shows a Hot Standby CPU on its rack with a power supply:

Accessing the Rack Viewer Page

Access the Rack Viewer page from the Diagnostics menu. In the navigation menu at the left side of the page, select Menu > System > Rack Viewer:

Rack Viewer page (HSBY CPU):

This example of a Rack Viewer page shows the Hot Standby connection between a primary CPU rack and a standby CPU rack. The Hot Standby connection (dashed line) is green when the Hot Standby link is healthy. If the Hot Standby link is not healthy, the dashed line is red.

Rack Viewer Data

Double-click on the Rack Viewer page to display Hot Standby CPU data.

Data Field

Description

Processor/Signature

RAM size (kb)

The size of processor RAM in KB

Processor Version

Firmware version

Hardware ID

An identifier for the module hardware. OS Loader checks this value to determine compatibility between the hardware and the operating system.

State

The operating state of the processor:

  • NO CONFIGURATION

  • IDLE

  • STOP

  • RUN

  • HALT

  • INITIALIZING

  • ERROR

  • OS LOADER

Error

The identity of the last detected error

Calendar (UTC)

Date and time of last detected error

Application

Name

Name of the Control Expert project

Version

Project version

Analog channel forced:

Indicates if one or more inputs or outputs for an analog channel have been forced:

  • True indicates the an analog input or output has been forced.

  • False indicates no analog input or output has been forced.

Diagnostic

Indicates if the diagnostic buffer has been activated for the project:

  • True indicates that Application diagnostics and/or System diagnostics has been selected in the General > PAC Diagnostics tab of the Project Settings dialog for the application.

  • False indicates Application diagnostics and System diagnostics have not been selected.

Forced bit

The number of forced bits in the application.

Creation Product

Includes both:

  • Version and build of Control Expert used to create the project.

  • Date and time the project was created.

Modification Product

Includes both:

  • Version and build of Control Expert used to edit the project.

  • Date and time the project was last edited.

Events Disabled

Indicates if all event processing has been disabled:

  • True indicates all event processing has been disabled.

  • False indicates event processing has not been disabled.

NOTE: Events can be enabled/disabled by using:
  • The Enable or Disable all command in the Task tab of the CPU.

  • The MASKEVT and UNMASKEVT functions.

  • System bit %S38.

Section protected

Indicates if password access is required to edit one or more sections of the application:

  • True indicates that a password is required to edit specified sections of the application.

  • False indicates that no password is required for application editing.

Automatic Start in Run

Indicates if the application is automatically set to start when the PAC goes into RUN operational mode:

  • True indicates the application automatically starts.

  • False indicates the application does not automatically start.

RAZ %MW on cold start

Indicates if %MW registers are reset to their initial values on a cold start:

  • True indicates that values are reset.

  • False indicates that values are not reset.

Cold Start only

Indicates if a cold start is forced on a system re-start:

  • True indicates that a reset forces a cold start of the application.

  • False indicates that a warm start will occur on application reset.

Creation Product

Includes both:

  • Version and build of Control Expert used to edit the project.

  • Date and time the project was created.

Modification Product

Includes both:

  • Version and build of Control Expert used to edit the project.

  • Date and time the project was last edited.