1 string file considerations, 2 substituting node names during synchronization, 3 replacing node name prefixes unconditionally – Micromod Micro-PWC: 53PW6000 MicroPWC Operators Manual User Manual

Page 161

Advertising
background image

Micro-PWC OPERATOR’S MANUAL

Utilities 147

for the printout of scheduled logs, and so on.

11.13.3.1 String File Considerations

String Files are the files which contain the text which apppears in the windows and on button faces, etc., on
the Micro-PWC displays. These files are typically used by system integrators when converting Micro-PWC
displays to a language other than English. Files in different languages are kept in separate directories.

Using the String Files option on the Console Group Synchronization Selection window will cause the string
files on the local node to be synchronized with those on the remote node. Synchronization will only occur if
the corresponding string file directory exists on the local node. Existing string files in that directory will be
overwritten if they share the same file name with string files on the remote node. (If no corresponding
directory exists, it will not automatically be created.)

11.13.3.2 Substituting Node Names During Synchronization

Node Names are used to identify the various nodes on the control network. Each node name is composed
of a three character descriptor which indicates the device type (e.g., PWC or CON), followed by the device
number (e.g., PWC6). Each node name on the network must be unique.

Node names are part of:

Historical Database configuration, where the configured node name denotes the storage node
for the data collected for each point in the Historical Database.

Historical Block Data Collection configuration, where the configured node name denotes the
storage node for the data collected for each historical block.

Printer Device configuration, where the node name reflects the node to which the printer
device is connected. (Note that a printer device can be a file or a hardware device.)

When console synchronization is performed on these types of configuration data, the node name remains
part of the configuration. The Node Names button provides a convenient way to change the node name in
the configuration as the material is synchronized. This allows the configuration to be easily adapted for use
on a node with a different name.

Click Node Names; the Node Names window will be displayed. Buttons at the top of the Node Names win-
dow allow the user to specify how the node name conversion will be performed on the configuration data
as it is synchronized. The options are:

New Global Operator Station Prefix

Specify Replacement Node Names

11.13.3.3 Replacing Node Name Prefixes Unconditionally

If New Global Operator Station Prefix is selected, the system will unconditionally replace the node name
prefixes in a configuration with a new prefix, as the data is synchronized. Selecting this item causes an
entry box to open. Note that this entry box is case sensitive.

Enter a three-character descriptor in this box. This descriptor will replace the original node name prefix in
Historical Database configuration data, Historical Block Data Collection configuration data, and Printer

NOTE

Note that some items in

Figure 11-44

are unavailable (stippled out);

the Network Device Assignment configuration is never
synchronized between console groups.

Advertising