● Precautions When Using FCN-500 or FCN-RTU with No Actual I/O
Modules
Resource configurator R4.20 or later can maintain unimplemented I/O module
definition.
If FCN-500 or FCN-RTU is not installed with the required I/O modules and new
hardware configuration us downloaded using Resource Configurator R4.10 or
earlier, existing I/O module configuration already defined will be overwritten and lost.
As an example, consider the following scenario.
An engineer defines the required device labels and I/O settings for target equipment
installed with the required I/O modules, and downloads the project to the FCN-500
or FCN-RTU.
However, as application creation and debugging is to be carried out using an in-
house FCN-500 or FCN-RTU, he relocates the CPU module on the target FCN-500
or FCN-RTU to the in-house FCN-500 or FCN-RTU and reboots the FCN-500 or
FCN-RTU.
When the engineer connects to the in-house FCN-500 or FCN-RTU using Resource
Configurator at this stage, the system reads a state of no I/O module.
The engineer then downloads this information using Resource Configurator,
resulting in I/O module information being overwritten, and information defined
previously is lost permanently.
To prevent this, it is advisable not to modify hardware settings using Resource
Configurator when working with no I/O module installed or from using a different set
of I/O modules than what is currently defined in the configuration.
● Using Resource Configurator Editor
Resource Configurator works by first reading configuration information from a
running FCN-500 or FCN-RTU, and then downloading new configuration information
after it has been modified on a PC. As such, it cannot be used to perform hardware
setup without a running FCN-500 or FCN-RTU.
To perform hardware setup when an FCN-500 or FCN-RTU is not available, such as
in the early phase of engineering or in a job involving modification of an existing
system, use Resource Configurator Editor instead.
Settings defined using Resource Configurator Editor can be saved to a file, and
downloaded later using Resource Configurator when the FCN-500 or FCN-RTU is
available for connection.