Siemens SIMATIC HMI OP 73micro Operating Instructions Manual page 163

Number Effect/cause
190007 The tag value is not modified because the
connection to the controller is interrupted or the tag
is offline.
190008 The threshold values configured for the tag have
been violated, for example, by
a value entered
•
a system function
•
a script
•
190009 An attempt has been made to assign the tag a
value which is outside the permitted range of
values for this data type.
For example, a value of 260 was entered for a byte
tag or a value of -3 for an unsigned word tag.
190010 Too many values are written to the tag (for
example, in a loop triggered by a script).
Values are lost because only up to 100 actions are
saved to the buffer.
190011 Possible cause 1:
The value entered could not be written to the
configured controller tag because the high or low
limit was exceeded.
The system discards the entry and restores the
original value.
Possible cause 2:
The connection to the controller was interrupted.
190012 It is not possible to convert a value from a source
format to a target format, for example:
An attempt is being made to assign a value to a
counter that is outside the valid, PLC-specific value
range.
A tag of the type Integer should be assigned a
value of the type String.
190100 The area pointer is not updated because the
address configured for this pointer does not exist.
Type
1 Warning alarms
2 Error alarms
3 Controller acknowledgment
4 HMI device acknowledgment
5 LED mapping
6 Trend request
7 Trend transfer 1
8 Trend transfer 2
No.:
consecutive number shown in WinCC flexible ES.
190101 The area pointer is not updated because it is not
possible to map the PLC type to the area pointer
type.
Parameter type and no.:
see alarm 190100
OP 73micro, TP 177micro (WinCC flexible)
Operating Instructions, 09/2007, 6AV6691-1DF01-0AB0
Remedy
Set online mode or reconnect to the controller.
Observe the configured or current threshold values of the
tag.
Observe the range of values for the data type of the tags.
Increase the time interval between multiple write actions.
Make sure that the value entered lies within the range of
values of the control tags.
Check the connection to the PLC.
Check the range of values or the data type of the tags.
Check the configuration.
-
Appendix
A.2 System alarms
163