Runtime errors

Top  Previous  Next

System messages

 

System messages are caused by special events. The system messages are logged in a logbook. The logbook can be displayed with the #LogView object.

 

Structure

Catalogue

System messages are combined in different catalogues (e.g. groups).

Class

Each message is assigned one of the following classes:

 

Class

Description

Explanation

Fatal

Fatal error
RTS must be shut down.
Indicated by a dialog.

For example, a resource is missing that the RTS relies on.

Error

Error
RTS does not have to be shut down in all cases.
Is displayed via a dialog.

e.g. syntax error in the project. The RTS can continue running, but this usually does not make sense in most cases.

Warning

Warning

RTS continues to run.
Not indicated by a dialog.

e.g. variable could not be read.

Info

Information

RTS running normally
Not indicated by a dialog.

Information messages such as Start/Stop of RTS.

 

 

 

 

Id

Number of the message

Time stamp

Date/time of message.

Text

Message text with parameters

 

Catalogues

Project
VarPool
Trend
Recipe
SysAdapter
PrgOption
Authent

 

 

Project catalogue

This catalogue contains messages that generally refer to the project files. Normally they indicate file and line number.

No.

Class

Text

Description

0

Error

file '<filepath>' failed to open

The file <filepath> could not be opened.

 

Cause:

Faulty project.

 

 

1

Error

file '<filepath>' failed to write

The file <filepath> could not be written.

 

Cause:

Path does not exist or medium is write protected.

 

Solution:

Adjust path.

2

Error

in file '<filepath>' line '<number>' incomplete

The line <number> in file <filepath> is not complete.

 

Cause:

Incorrect or damaged project file.

 

Solution:

Recompile project.

3

Error

language file '<filepath>' in line '<number>' inconsistent

The language file does not match the project file. The error is at line <number> in language file <filepath>.

 

Cause:

 

 

Solution:

 

4

Error

in file '<filepath>' line '<number>'

undefined action <text>

Action <text> on line <number> in file <filepath> is undefined.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

5

Error

in file '<filepath>' line '<number>'

undefined limit action '<text>'

Limit action (1/2) <text> on line <number> in file <filepath> is undefined.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

6

Error

in file '<filepath>'

section '<text>' not found

Section <text> in the file <filepath> not found. Section stands for #page=<name>, #Group=<name>, #scrollist=<name>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

7

Error

in file '<filepath>' line '<number>'

invalid library definition '<text>'

The library definition <text> in file <filepath> on line <number> is invalid.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

8

Error

in file '<filepath>' line '<number>'

invalid library path '<path>'

The library path <path> in file <filepath> on line <number> is incorrect.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

9

Error

in file '<filepath>' line '<number>'

undefined variable type '<text>'

In file <filepath> on line <number> invalid data type <text>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

10

Error

in file '<filepath>' line '<number>'

invalid com-driver parameters <text>

In file <filepath> on line <number> invalid communication driver parameters <text>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

11

Error

in file '<filepath>' line '<number>'

invalid variable definition: '<text>'

In file <filepath> on line <number> variable definition <text> is invalid.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

12

Error

in file '<filepath>' line '<number>'

undefined com-driver name '<text>'

In file <filepath> on line <number> undefined communication driver name <text>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

13

Error

in file '<filepath>' line '<number>'

undefined host name '<text>'

In file <filepath> on line <number>

undefined host name <text>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

14

Error

in file '<filepath>' line '<number>'

failed to register variable '<text>'

In file <filepath> on line <number>

Variable could not be registered.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

15

Error

in file '<filepath>' line '<number>'

variable '<name>' type '<type>' conflict

In file <filepath> on line <number>

The data type <type> does not match the data type of the variable <name>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

16

Error

in file '<filepath>' line '<number>'

type '<type>' of variable '<name>' not supported

In file <filepath> on line <number>

The data type <type> of the variable <name> is not supported.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

17

Error

in file '<filepath>' line '<number>'

bad action argument '<text>'

In file <filepath> on line <number>

Invalid argument in action <text>

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

18

Error

in file '<filepath>' line '<number>'

undefined option '<text>'

In file <filepath> on line <number>

Invalid option <text>.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

19

Error

in file '<filepath>' line '<number>

undefined font '<text>'

In file <filepath> on line <number>

Undefined font <text>

20

Error

in file '<filepath>' line '<number>'

unrecognized syntax '<text>'

In file <filepath> on line <number>

Invalid syntax

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

21

Error

in file '<filepath>' line '<number>'

action '%3' failed

In file <filepath> on line <number>

The action <text> has failed

 

Cause:

It depends on the relevant action. For example, the action system=<cmd> may have failed because the stated path is not correct.

 

 

Solution:

Adjust configuration or environment.

22

Error

in file '<filepath>' line '<number>'

error in description %3 '%4'

In file <filepath> on line <number>

Error in description <description> '<text>'

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

23

Info

start project '<filename>'

Start of the RTS with project file <filename>

 

VarPool catalogue

This catalogue contains messages that refer directly to variables,types and communication.

No.

Class

Text

Description

0

Error

type <type1> conflicts '<type2>' with type for variable '<name>'

This message is only for internal use.

1

Error

unable to load driver '<name>': '<text>'

The communication driver <name> could not be loaded. Extended error message displayed in <text>.

 

Cause:

RTS is not correctly installed.

 

Solution:

Execute installation.

 

2

Error

driver '<name>' is incompatible

The communication driver <name> is not compatible with the RTS.

 

Cause:

RTS is not correctly installed.

 

Solution:

Execute installation.

 

3

Warning

Channel '/<driver>/<host>' disturbed: '<text>'

The communication channel /<driver>/<host> is faulty. An extended error message is displayed in <text>.

 

Cause:

RTS is not correctly installed.

 

Solution:

Execute installation.

 

4

Info

Channel '/<driver>/<host>' connected

The communication channel /<driver>/<host> was successfully connected.

5

Warning

Variable '<name>' read error '<text>'

The variable <name> can not be read. Extended error message displayed in <text> {addresserror|typeconflict}

 

Cause:

Variable does not exist in the PLC or has a different data type.

 

Solution:

Adjust EPAM or PLC project.

6

Info

Variable '<name>' read ok

The variable <name> was read successfully.

 

Cause:

Variable could be read after it previously could not be read.

 

7

Error

Variable '<name>' write error

The variable <name> can not be written.

 

Cause:

Variable does not exist in the PLC or has a different data type.

 

Solution:

Adjust EPAM or PLC project.

 

8

Warning

Variable '<name>' write ok

The variable <name> was written successfully.

 

Cause:

Variable could be written after it previously could not be written.

 

 

Trend catalogue

This catalogue contains messages that refer directly to a #Trend object

No.

Class

Text

Description

0

Error

Trend <name>: undefined Datalog '<text>'

Trend <name>: Datalog <text> not defined.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

1

Error

Trend <name>: Y range of curve '<text>' is invalid

Trend <name>: The Y axis of the curve <text> is invalid.

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

2

Error

Trend <name>: X range is invalid

Trend <name>: X axis is invalid

 

Cause:

Configuration error.

 

Solution:

Correct configuration:

 

 

SysAdapter catalogue

This catalogue contains messages that refer directly to the SysAdapter. The SysAdapter (normally SysAdapter.dll)  is an RTC component in which platform-specific functions are implemented.

No.

Class

Text

Description

0

Fatal

sysplug '<filepath>' load error: '<text>'

SysPlug <filepath> could not be loaded. Extended error message in <text>

 

Cause:

The installation of the RTS is faulty.

 

Solution:

Repeat the installation.

1

Fatal

failed to initialize the touch device

The touch device could not be initialized.

 

 

 

Recipe catalogue

This catalogue contains messages that refer directly to a #Recipe object

No.

Class

Text

Description

0

Error

Couldn't load recipe '<filepath>':

XML error: '<text>'

Recipe file <filepath> could not be loaded:

The error <text> occurred when parsing the XML file.

 

Cause:

Damaged file or invalid XML file.

 

Solution:

Remove file.

1

Error

Couldn't load recipe '<filepath>':

Recipe type '%2' doesn't match

Recipe file <filepath> could not be loaded:

The recipe type <type> does not match.

 

Cause:

The file may have been copied to the target by hand.

 

Solution:

Remove file.

2

Error

Couldn't load recipe '<filepath>':

Variable count '<number>' doesn't match

Recipe file <filepath> could not be loaded:

Number <number> of variables does not match.

 

Cause:

The recipe may have been changed, variables added or removed.

 

Solution:

The error dialog provides 3 options.

 

[Ignore]

The recipe file is loaded anyway (possibly incomplete).

 

[Delete]

The recipe file is not loaded and is deleted.

 

[Cancel]

The recipe file is not deleted.

 

3

Error

Couldn't load recipe '<filepath>':

Type '<type>' for variable '<name>' not supported

Recipe file <filepath> could not be loaded:

The data type <type> for variable <name> is not supported.

 

Cause:

Configuration error: Arrays, for example, are not supported.

 

Solution:

Correct configuration.

 

4

Error

Couldn't load recipe '<filepath>':

Type conflict for '<name>', expected '<type1>' found '<type2>'

Recipe file <filepath> could not be loaded:

Type conflict variable <name>, <type1> expected, <type2> found.

 

Cause:

The recipe was changed, perhaps the recipe file is obsolete.

 

Solution:

The error dialog provides 3 options.

 

[Ignore]

The recipe file is loaded anyway (possibly incomplete).

 

[Delete]

The recipe file is not loaded and is deleted.

 

[Cancel]

The recipe file is not deleted.

 

5

Error

Couldn't load recipe '<filepath>':

Variable '<name>' is unknown

Recipe file <filepath> could not be loaded:

Variable <name> is unknown.

 

Cause:

Obsolete recipe.

 

Solution:

The error dialog provides 3 options.

 

[Ignore]

The recipe file is loaded anyway (incomplete).

 

[Delete]

The recipe file is not loaded and is deleted.

 

[Cancel]

The recipe file is not deleted.

 

6

Error

Couldn't load recipe '<filepath>':

Project name '<name>' doesn't match

Recipe file <filepath> could not be loaded:

Project name <name> does not match the project.

 

Cause:

The recipe file comes from a different project

 

Solution:

Remove recipe file.

 

7

Error

Recipe '<type>' download error at variable '<name>'

Error when writing the variables of the recipe <type> to the PLC:

Variable <name> could not be written.

 

Cause:

The variable <name> does not exist in the PLC

 

Solution:

Adjust EPAM or PLC project.

 

8

Error

Recipe '<type>' upload error at variable '<name>'

Error when reading the variables of the recipe from the PLC:

Variable <name> could not be read.

 

Cause:

The variable <name> does not exist in the PLC

 

Solution:

Adjust EPAM or PLC project.

 

9

Error

Invalid recipe definition file '<filepath>'.

Error in line '<number>'

Invalid recipe definition file <filepath>. Error in line <number>.

 

Cause:

File is damaged.

 

Solution:

Execute new Build.

 

10

Info

Recipe '<type>' file 'filepath' loaded

File <filepath> of the recipe <type> was successfully loaded.

 

11

Warning

Recipe '<type>' incompatible file '<filepath>' loaded

The incompatible file <filepath> of the recipe <type> was loaded.

This message is a consequence of the Acknowledgement dialog with [Ignore] message 2, 4 and 5

12




 

PrgOption catalogue

This catalogue contains messages that refer directly to the RTS parameters (Command line, EPAM.INI).

No.

Class

Text

Description

0

Fatal

invalid command line argument syntax: '<text>'

The syntax of the Parameters command lines <text> is invalid.

1

Fatal

Inifile '<filepath>' not found

The Ini file <filepath> does not exist.

2

Fatal

PATH_RAM parameter '%1' invalid

The RAM_PATH in EPAM.INI is invalid.

 

Cause:

The path is incorrectly configured. The absolute path must be specified.

 

Solution:

Correct the path.

 

Authent catalogue

 

No.

Class

Text

Description

0

Info

user '<name>' logged in"

The user <name> has logged in.

1

Warning

login '<name>' failed

The user <name> could not log in.

 

Cause:

- Incorrect password

- Account disabled

 

2

Info

user '<name>' logged out

The user <name> has logged out.

3

Info

user '<name>' has changed his password

The user <name> has changed his password.

4

Warning

changing password for '<name>' failed with error# '<number>'

Changing the password for <name> failed with error# <number>