Siemens Multi Panel MP270 SIMATIC HMI Equipment Manual page 103

Number
20011 An error has occurred in a script called in by the script
specified. Execution of the script function has,
therefore, been terminated in the subscript.
In this case, it is advisable to check any previous
system messages too.
20012 Inconsistent configuration data is present. Therefore,
the script could not be created.
20013 VBScript.dll is not correctly installed. Therefore, no
scripts can be executed.
20014 A value is returned by the script function which is not
written in any configured return tag.
20015 Too many scripts have been triggered in quick
succession.
If more than 20 scripts are queued to be processed,
any subsequent scripts are rejected.
In this case, the script indicated in the message is not
executed.
30010 The tag could not accept the function result, e.g. in
the case of exceeding the value range.
30011 A function could not be executed because the
function was assigned an invalid value or type in the
parameter.
40010 The function could not be executed since the
parameters could not be converted to a common tag
type.
40011 The function could not be executed since the
parameters could not be converted to a common tag
type.
50000 The operating unit receives data faster than it is
capable of processing. Therfore, no further data is
received until the data currently available has been
processed. Data exchange then resumes.
50001 Data exchange has been resumed.
60000 This message is generated by the function "Display
system messages". The text to be displayed is
transferred to the function as a parameter.
60010 The file could not be copied in the direction defined
because either one of the two files is currently open or
the source/target path is not available.
It is possible that the Windows NT user has no access
rights to one of the two files.
MP270 Equipment Manual
Release 01/99
Effect/Cause
System Messages
Remedy
Select the scripts from the
configuration which were directly or
indirectly called in via the specified
script.
Check tags, whether the types
used are permissible.
Check Functions, whether the
number and types of parameter
are correct.
Compile the configuration again.
Re-install ProTool/Pro RT.
Select the specified script in the
configuration.
Check whether the script name
has been assigned a value.
Check where the scripts are being
triggered from.
Extend the times, e.g. the polling
time of the tags, which trigger the
scripts.
Check the tag type of the function
parameter.
Check the parameter value and tag
type of the invalid parameter.
If a tag is used as a parameter,
check its value.
Check the parameter types in the
configuration.
Check the parameter types in the
configuration.
–
–
–
Restart the function or check the
paths of the source/target files.
Using Windows NT with NTFS:
The user executing ProTool/Pro RT
must be granted access rights for
the files.
C-3