Causes of runtime errors for a numeric pop-ups

At runtime, the application logs error messages about the numeric pop-ups to diagnostics under the following circumstances. These are common causes, but because of the wide variety of possible applications, other conditions not mentioned here may also cause error messages.

Value beyond the Value limit

Value too large for the Value connection

If the value is too large for the data type of the tag assigned to the Value connection, or if the value is outside the assigned tag's minimum and maximum values, when the operator presses the

Enter

button:

For example, the value is too large for the tag’s data type if the data source is a

PLC-5

, the value is 2147483647, and the assigned tag is an integer tag using the address N7:0. Integer tags have a range of -32768 to 32767 only.

Value outside minimum and maximum range

The displayed value with the decimal point stripped is compared to the minimum and maximum range for Fixed Position using the Stripped Value option. The shown value with decimal point is compared to the minimum and maximum range for Implicit and for Fixed Position using the

Displayed Value

option. If the value is outside the minimum and maximum range (specified in the

General

tab for the numeric input enable button), when the operator presses the

Enter

button:

Enter key handshaking still in effect

If timing for Enter key handshaking from a previous pop-up entry is still in effect when the operator presses the

Enter

button:

Screen resolution too small

If the screen is too small to display the numeric pop-up, the application logs an error.

Invalid Optional Expression

If the optional expression assigned to the object is invalid or not assigned, when the operator presses the

Ente

r button:

Invalid initial value

If the initial value shown is based on the Value connection, and the initial value is invalid, the pop-up's scratchpad will show asterisks to indicate an error condition. The application will not log an error.