YOKOGAWA STARDOM FCN-100/FCJ Migration Technology

YOKOGAWA STARDOM FCN-100/FCJ Migration Technology

Migration core principles and limitations

（1） Core migration logic

The essence of migration is the process of "adaptation transformation deployment" of source device configuration and application:

Data level: Backup the configuration data (resource configuration, system files) of NFCP100/NFJT100, convert it to NFCP500 compatible format, and then restore it to the target device;

Application level: Upgrade the control projects (R1-R4 versions) in Logic Designer, adapt them to PLC/processor types, recompile and download them to the target device;

Special configuration: Field bus definition and Duolet application need to be separately adapted to the hardware interface and system file format of the target device.

（2） Key Limitations and Rules

Data compatibility:

The FcxConvert command only supports NFCP100 backup file conversion, NFJT100 backup files cannot be converted, and I/O definitions and DUONUS.PRP files need to be reset;

When expanding the hold data area, the hold data saved by NFCP100 cannot be used for NFCP500 and needs to be reconfigured;

Control applications, launch projects, and source files that do not participate in FcxConvert conversion need to be compiled and downloaded separately through Logic Designer.

License restriction: The source device license cannot be migrated to FCN-500, and the CPU module of the target device must be pre bundled with the required license.

IP address inheritance: When restoring converted data, the target device's IP address will automatically inherit the source device's IP address. If modification is required, it needs to be adjusted through the Resource Configurator after recovery.

Hardware interface adaptation: The COM2 port of FCJ needs to be migrated to the RS-232C communication module, and the port name in the application needs to be changed from "COM2" to the module configuration name (such as "RS02").

Detailed explanation of core migration tools and commands

（1） Command line tool functions and usage

Complete syntax and key instructions for the core functions of tool commands

FcxBackup backup source device (NFCP100/NFJT100) data FcxBackup - all - u<username>- p<password><hostname/IP>1. The "- all" parameter requires R3.10+version, and the "- u/- p" parameter requires R4.10+version;

2. Generate a "BACKUP" folder containing data files, resource configuration, DUONUS.PRP, etc;

3. Example: FcxBackup all - u user01- p abc123 192.168.0.1

FcxConvert converts NFCP100 backup files to the target device format FcxConvert.exe - t<NFCP501/NFCP502>- i<source folder>- o<target folder>1. The source folder defaults to "ACKUP", and the target folder needs to be customized (such as "ACKUP_CFCP501");

2. After conversion, the target folder needs to be renamed as "ACKUP" before it can be used for recovery;

3. Example: FcxConvert.exe - t NFCP501- i BackUP - o BackUP_CFCP501

FcxRestore restores the converted data to the target device FcxRestore<hostname/IP>1. Before restoring, it is necessary to clear the hold data in the SRAM of the target device (in conjunction with FcxSaveRetain-c);

2. Example: FcxRestore 192.168.0.1

FcxSaveRetain saves/clears hold data FcxSaveRetain-c<hostname/IP>1. Only use the "- c" parameter during migration (clear SRAM hold data);

2. Ensure that the backup data is correctly mapped to the target device SRAM;

3. Example: FcxSaveRetain - c 192.168.0.1

（2） Tool acquisition and directory structure

Acquisition steps:

Insert R4.20+version system DVD ROM;

Select "DVD Contents" and double-click on "FCN/FCJ Basic Software Package" (FCN-500 corresponds to Pkg.NFCP500. exe in the Pkg.NFCP500 folder);

Specify the installation folder (such as "C: temp"), extract it, and generate the tool files.

Typical directory structure:

plaintext

C:temp

⊙ - NFCP500 # Core Tools Folder

│∝ - FcxBackup.exe # Backup Command

│∝ - FcxConvert.exe # Conversion Command

│└ - FcxRestore.exe # Restore Command

└ - FCXTOOL # Auxiliary Tools Folder

∝ - FcxSaveRetain.bat # Keep Data Processing Batch Processing

└ - save_record. txt # Configuration file

Control the core rules for application migration

（1） PLC type matches processor type

PLC type processor type migration operation (without expanding the hold data area) migration operation (expanding the hold data area) applicable scenarios

IPC40 FCX/FCX_A can be directly recompiled without modifying the project reconstruction resources (PLC=IPC40, processor=FCX_B/FCX_C)+compiling the original configuration of NFCP100, which needs to be expanded to maintain data

IPC32/IPC33- Rebuilding Resources (PLC changed to IPC40)+Copying Configuration (tasks/variables/labels, etc.)+Compiling Rebuilding Resources (PLC=IPC40, processor=FCX_B)+Copying Configuration+Compiling Low Version PLC Type Adaptation Target Device

SH_40- Rebuilding Resources (PLC changed to IPC_40)+Compilation - SH_40 Type Compatibility Upgrade

（2） Processor type description

Processor type applicable to device core characteristics

FCX NFJT100/NFCP100 does not support modules such as NFLF111/NFGS813