Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Plant SCADA

Compile Warning Messages

  • Last UpdatedAug 12, 2024
  • 8 minute read

If the Type specified for a compile message is WARNING, it means something was detected that did not stop the project from compiling successfully, however, further investigation is recommended. For information on how to address a WARNING message, use the code included in the error description (for example, "W1001") to locate the warning message in the following table.

If the Type specified for a compile error message is ERROR, see the topic Compile Error Messages.

If the Type specified for a compile error message is FATAL, see the topic Compile Fatal Messages.

Note: You can disable a warning using the parameter [CtEdit]SuppressCompilerWarning.

Code

Warning Message

Description

W1001

No IO Devices defined

No I/O devices have been defined in this project or any of its included projects (see Add an I/O Device).

W1002

Include project not found

An included project (specified in the Included Projects database) does not exist. Check the name of the included project. For more information, see the Included Projects section in Project Types.

W1003

Argument with default found before argument with no default

This error will occur when a Cicode function is defined with a default argument before an argument without a default. For example:

INT
FUNCTION LogFieldValue(string sFile, string sField = """", string sValue)

END


In this case, you will need to review how this function is used and either add a default value to argument sValue or remove the default from the argument sField. For example:


INT
FUNCTION LogFieldValue(string sFile, string sField = """", string sValue = """")

END

or


INT
FUNCTION LogFieldValue(string sFile, string sField, string sValue)

END

W1004

Incorrect number of arguments for function

Too many or too few arguments have been passed to a Cicode function.

W1005

Tag may be unused

A tag that is included in your project in not referenced and appears to serve no purpose. Consider removing the tag, or add the required reference to the tag.

W1006

Function has the same name as built-in function

A Cicode function name within the project has the same name as an in-built Cicode function. It is recommended that you rename your function. You can then use the find and replace dialog to update any references to the original function name.

W1007

Tag not defined

The compiler has detected a reference to a tag that does not exist. You should create the required tag, or update the reference.

W1008

Function deprecated, legacy function will be removed in a future release

A Cicode function that is used in your project has been deprecated, which means it will be made obsolete in a future release. You should consider replacing the Cicode function.

W1009

Function deprecated, can only be called on the Server

A Cicode function that is used in your project has been deprecated, which means it will be made obsolete in a future release. Currently, you can only call the function on a server. You should consider replacing the Cicode function.

W1010

Function deprecated, does not support online changes made to the system

A Cicode function that is used in your project has been deprecated, which means it will be made obsolete in a future release. Currently, the function does not support online changes. You should consider replacing the Cicode function.

W1011

Alarm Tag not found, but valid property detected. Tag may not be available at runtime

The project refers to an alarm property that is associated with an alarm tag that does not exist. Create the specified alarm tag, or confirm that it is available on the alarm server.

W1012

Standby IODevice did not have a priority specified

The specified standby I/O device requires a priority setting.

W1013

Could not launch post compile command

Plant SCADA was unable to execute a command, script or batch file that was specified to run when compilation is complete. Check the replacement strings used for the parameters [CtEdit]CompileSuccessfulCommand and [CtEdit]CompileUnsuccessfulCommand to determine what occurred.

W1014

The tag and a cluster have the same name. It may lead to unintended behavior

Plant SCADA may behave unexpectedly if you use a tag name that is the same as a cluster name. You should rename the specified tag.

W1015

IODevices for this unit number mix different protocols

I/O devices with the same unit number must all use the same protocol.

W1016

IODevices for this unit number mix disk and non-disk types

I/O devices with the same unit number must either be all disk devices, or all non-disk devices.

W1017

IODevices for this unit number mix memory and non-memory modes

I/O devices with the same unit number must either be all memory or all non-memory.

W1018

File does not exist

The compiler has detected a reference to a file cannot be found. Check that the file is available, and that name used is correct.

W1019

Multiple translations for the same native string

Multiple translations for a native string have been detected in the language database(s). You should review the language databases associated with your project (including those in any included projects), and remove any duplications.

W1020

Duplicate language

A language has been defined multiple times. You should check the languages specified in your project (including those in any included projects) and remove the duplication.

W1021

Possible missing operand between tags

The compiler has detected some incorrect Cicode syntax. For example, an operand may be missing between a tag and a constant.

W1022

Possible address on bad boundary

When the compiler finds a double-register variable, it remembers which boundary it is on and checks that all other double register variables are on the same boundary. This message will appear if the address of a long or real variable is not aligned correctly. For more information, see [General]CheckAddressBoundary.

W1023

Void functions are not supposed to return values

The Cicode function uses the keyword RETURN but the function header does not contain a return type.

For example:

FUNCTION LogFieldValue(string sFile, string, sField, string sValue)
...
Return = FileOpen(sFile, "a+")
IF iReturn = -1 THEN
RETURN -1;
END
...
END

Change this function to the following:

INT
FUNCTION LogFieldValue(string sFile, string, sField, string sValue)
...
iReturn = FileOpen(sFile, "a+")
IF iReturn = -1 THEN
RETURN -1;
END
...
END

W1024

Duplicate settings for LocalLanguage

The compiler has detected that the local language setting is duplicated across the main project and its included projects. This means the language databases associated with each project would have been merged during compilation. For more information see Define the Languages Supported by a Project.

W1025

The specified language is not defined in the language form

Your project refers to a language that is not specified in the Languages view in the Setup activity. You need to define the language in your project (see Define the Languages Supported by a Project).

W1026

Unsupported file extension type

A file that is referred to in your project includes an extension type that is not recognized by Plant SCADA. Firstly check that the file extension is correct in the point of reference. If it is, it means the file type is not supported; you should remove the reference.

W1027

The specified language is not supported

Your project refers to a language that is not supported by Plant SCADA by default. You should use a supported language instead, or add support for the language to your project (see Define an Unsupported Language).

W1028

Unsupported syntax for marking translation text, it will not be translated

The compiler has detected that incorrect syntax has been used to mark some text for translation. Review the syntax used and make any required changes. For more information on correct syntax for marking translation text, see Mark Text for Translation and/or Mark Alarm Text for TransltionP.

W1029

Not a valid language

A language that has been defined in your project is not recognized by the compiler. Check the Languages Properties settings (see Define the Languages Supported by a Project).

W1030

This parameter overrides another with different value in one of the subprojects

A system parameter setting in the project database has also been detected in an included project. It is recommended you remove any duplicated system parameter settings from the included project(s).

W1032

'Allow RPC' permission is not defined (defaulting to FALSE)

The Allow RPC property for a Role determines if a user or group of users can perform remote MsgRPC or ServerRPC calls. When upgrading projects, this field is left blank which will raise the compiler warning message.

To allow existing users to continue using MsgRPC and ServerRPC, you need to manually change the value of Allow RPC to TRUE in Plant SCADA Studio’s Security | Roles view.

If these functions are used in your project, the roles that execute the functions will also need to have the permissions enabled.

W1033

Length of the vertex path is zero

The From Offset and To Offset values specified for the polyline vertex are the same; therefore, the length of the vertex path is zero.

W1034

Transparent colors are not supported

A transparency setting is applied to a color that has been specified for an Alarm Priority display property. Transparency is not supported for Alarm Priority color settings.

W1035

'Allow Exec' permission is not defined (defaulting to FALSE)

"Allow Exec" on the Role form determines if a user or group of users can perform Exec calls in runtime. When upgrading projects if this field is left blank, the compiler warning message will be displayed.

W1036

'Manage User' permission is not defined (defaulting to FALSE)

"Manager User" on the Role form determines if a user or group of users can update user security settings at runtime. When upgrading projects if this field is left blank, the compiler warning message is displayed.

W1037

IO Server is not defined

The Server Name referenced by the I/O device is not defined in the IO servers table.

W1039

Tag usage is ambiguous; Tag exists for two or more clusters. Add cluster name to resolve.

An ambiguous tag is detected because multiple tags with the same name exist in different clusters, and the cluster name has not been specified as part of the tag name.

W1040

Numeric user names are not supported

When the user name contains only digits, for example, "12345", this message is displayed at runtime because a numeric user name is not valid.

W1041

TLS exchange, if enabled, cannot succeed using an IP address

The TLS exchange does not succeed if encryption is enabled for your system and the Address field in the Network Addresses table is set to an IP address.

To resolve this, configure the computer name of the server in the DNS Name field in the Computers table.

Note: This step is not required if the Address field in the network address table is configured with a computer name.

W1048

Reserved Keyword is being used

Tag, equipment or cluster name contains Reserved Words.

W1049

Equipment parameters should be migrated to Configuration Parameters

The compiler has detected legacy custom parameters in your project. It is recommended that you migrate these to configuration parameters (introduced in Plant SCADA 2023). For more information, see Migrate Custom Parameters to the Configuration Parameters Database.

Note: This warning message will only be reported the first ten times an occurrence is detected.

W1050

Unique ID expected. Please run Migration Tool.

The compiler has detected equipment and/or variables that do not have a unique ID assigned to them. Run the Project Migration Tool with the Create unique IDs for Variables and Equipment option selected.

For more information, see Unique IDs for Variable Tags and Equipment.

Note: This warning message will only be reported the first ten times an occurrence is detected.

W1051

User 'Kernel' does not have Full Access to the Kernel window.

The legacy 'Kernel' user that enabled Kernel access in previous versions of Plant SCADA no longer has default access to the Kernel window in version 2023 R2 (or later).

It is recommended that you delete this user and access the Kernel through a Plant SCADA or Windows user account. See Display the Kernel Window.

W1052

Parameter name is empty

The Name field for an Equipment Configuration Parameter is empty. The equipment runtime database will not include this parameter.

Related Links
TitleResults for “How to create a CRG?”Also Available in