E - validation messages, Validation messages, Appendix – Rockwell Automation 2711-ND3 PanelBuilder v2.60 Software User Manual User Manual

Page 455

Advertising
background image

Appendix

E

Publication 2711-6.0

Validation Messages

This appendix lists error messages that appear during a validation or
download operation. Messages are listed alphabetically.

Validation Message

Meaning

What to do

Ack Tag must have BCD, signed int, or
unsigned int data type.

An invalid data type was selected for the
alarm acknowledge tag.

Change tags or the data type. Valid data
types are BCD, signed integer, or unsigned
integer.

Ack Tag range must be greater than or equal
to trigger range.

The number of bits in the ack tag’s data
length must be greater than or equal to the
number of data bits for the trigger.

Increase the number of bits in the Alarm
Acknowledge tag.

Acknowledge all value must be greater than
highest bit position for this trigger.

For bit and least significant bit alarm triggers,
the acknowledge all bit position must be at
least one greater than the highest bit
specified for the alarm.

Increase the bit position specified for the
acknowledge all field.

Acknowledge all value used as alarm trigger
value/bit.

Acknowledge all value for the trigger is the
same as one of the values that triggers an
alarm.

Choose a unique value/bit for the
acknowledge all value.

Address overlaps Block Transfer/Pass Thru
Control Byte

A tag is assigned the same address as the
Block Transfer Control Byte (the lowest
accessible byte in the discrete I/O rack).

Enter a different address for the tag in the Tag
Editor or disable block transfers (if not using
BTs) in the Block Transfer dialog.

Alarm List queue size too large for remaining
NVRAM space.

The specified size of the alarm list queue is
too large for the available memory.

Specify a smaller alarm list queue size.

Alarm requiring acknowledgement must be
displayed.

An alarm acknowledge button is defined but
the alarm is not enabled for display.

Enable the alarm for display.

Alarm Trigger cannot be the same as the
acknowledge or handshake tags.

The alarm trigger is assigned the same tag
name as the Ack or Handshake tag.

Change the tag names so they are unique.

Alarms requiring acknowledgement cannot be
acknowledged individually from the alarm list
without the Enter list key.

An alarm that can be acknowledged in the
alarm list does not have an Enter list key on
the screen.

Add an Enter list key to the specified screen.

All states in this object refuse operator entry.

All states of the piloted control list have an
access of “Controller Only” or ”None”. This
is illegal.

Open the object’s dialog and change the
access for some of the states to “User and
Controller” or “User Only”.

An alarm ack button must exist.

There is an alarm that requires and
acknowledgement (ack) button.

Add an alarm acknowledge button to the
alarm banner.

An alarm clear button must exist

An alarm that does not require
acknowledgement exists. A clear button must
be defined to clear the alarm.

Add alarm clear button to the alarm banner.

An alarm banner must exist.

An alarm banner is not defined and an alarm
is enabled for display.

Turn off the display for the alarm or create an
alarm banner for the application.

Application translation failed – a Screen uses
too many Terminal Resources.

A screen contains too many controls and
indicators.

Redesign the screen with fewer control or
indicator objects.

Application type does not match terminal
type. Re-configure in Terminal Setup.

The application is configured for Remote I/O
or DH-485 communications but the selected
terminal type does match.

From the Setup tab in Terminal Setup, select
a terminal type that matches the application.
Or convert the application to match the
terminal type. Then update the tags.

At least one alarm must be configured to use
this object.

An alarm device exists which requires an
alarm to be configured.

Remove the device or add alarms to the
application.

Advertising