EOS SCADA Reserved Characters

The characters considered reserved in EOS SCADA software are listed below. It is important to avoid using these characters particularly in text fields such as tag names, device names, connection information, parameters, descriptions, and similar fields in order to ensure more predictable system behavior and preserve the integrity of configuration data.

Important: The use of reserved characters may be prevented by software-based filtering in some text parameters. However, it is recommended not to rely solely on filtering and to avoid these characters from the design stage onward.

Character Name Description
| Vertical bar May be interpreted as a special character used to separate data or text sections.
: Colon May have a special meaning when parsing parameters or information fields.
; Semicolon May be interpreted as a delimiter for separating multiple values or parameters.
, Comma May have a special meaning when separating lists or values.
. Period May have a special meaning in fields, names, or numerical representations.
@ At sign May conflict with specially formatted identifiers or text structures.
+ Plus sign May have a special meaning as an operator or within an expression.
- Minus sign May be confused with an operator, sign, or range notation.
/ Slash May be used for special purposes as a delimiter or within an expression.
* Asterisk May be interpreted as a wildcard character or operator.
= Equals sign May conflict with assignment or comparison expressions.
& Ampersand May have a special meaning in expressions or special character representations.
% Percent sign May be associated with formatting or special expression structures.
( Opening parenthesis May be interpreted as the beginning of an expression or function.
) Closing parenthesis May be interpreted as the termination of an expression or function.

Use in Text Fields

The primary risk of using reserved characters in text fields is that a value considered by the user to be a single text string may be interpreted by the software as multiple sections, parameters, or expressions. In such cases, even if the entered information appears correct, unexpected results may occur during storage, reading, querying, or reloading.

Recommended Approach:

For device, tag, and parameter names, a simpler and more consistent naming approach is recommended, using names composed of letters and numbers instead of reserved characters.

The objective is not merely to restrict user input. The main objective is to ensure that configuration information, data transfer mechanisms, and database records are processed while preserving the same meaning throughout the system.

Design and Database Integrity

Avoiding reserved characters is not merely a matter of usability in the design of an EOS SCADA system. It is also important for database integrity, data transfer between systems, and long-term maintenance.

Basic Approach for Reliable Design:

  • Avoid reserved characters in tag, device, and parameter names.
  • Use simple and consistent naming conventions in text fields.
  • Maintain the same naming convention for values transferred between different EOS modules.
  • Do not assume that reserved characters are safe simply because a filtering mechanism is available.
  • Define naming conventions at the beginning of the project design process.

Particularly in large SCADA projects involving a large number of data points, simple and consistent naming conventions established at the beginning can reduce potential data inconsistencies and maintenance costs in the future.

Complete Reserved Character List

For quick reference, the characters recommended to be avoided in EOS SCADA are:

| : ; , . @ + - / * = & % ( )

As a general design approach, avoiding these characters in text parameters helps make EOS SCADA configurations more predictable and maintainable.

← Back to Previous Content