YOKOGAWA STARDOM FCN-100/FCJ Migration Technology

FCX_A NFCP100 supports modules such as NFLF111/NFGS813

FCX_B NFCP501/NFCP502 Extended version of FCX_A for maintaining data area

FCX_C NFCP501/NFCP502 supports 3 or more expansion units+NFLF111 and other modules, with device label expansion versions

（3） Project upgrade and compilation

Version compatibility: R1-R3 version projects are automatically converted to R4 format when opened with Logic Designer R4, and cannot be backward compatible with lower version tools after conversion;

Key points of resource reconstruction:

Copy the task definition, global variable definition, device label variable definition, software wiring definition, etc. of the original project;

Configure target device parameters (such as IP address, communication port);

If using a user library, you need to copy the. mwt file and the folder with the same name to "C: YOKOGAWA FCN-FCJ LogicDesigner Libraries", compile and register it;

Download requirements: Perform offline downloads (including controlling applications, launching projects, source files), ensuring that the target device is in online mode.

Detailed process of two migration modes

（1） Mode 1: migrate directly to the target device (complete the whole process on site)

Applicable scenarios: on-site downtime allowed, no need for prior verification, no complex field bus configuration

Core steps (10 steps)

Key precautions for step-by-step operation content

A1 obtains the installation folder of the conversion tool without spaces, and after decompression, confirms the integrity of the tool

A2 Save NFCP100 Keep Data Login STARDOM Maintenance Page → Maintenance Menu → Save Retain Data → Click [SAVE]; No [SAVE] button in maintenance mode

Switch the command line of A3 backup NFCP100 data to the tool directory, execute the FcxBackup command, and generate the "ACKUP" folder

A4 Convert backup file (NFJT100 skip) Execute the FcxConvert command, rename the destination folder to "ACKUP"

Replace the CPU module with A5, remove the NFCP100, and transfer the Ethernet/RS-232-C cable (connect the Ethernet to the original 1/2 port); The new NFCP500 requires setting the IP address through the Resource Configurator first

A6 target device switches to maintenance mode, logs in to Maintenance Page → Reboot → Reboot (Maintenance Mode) → Confirm startup mode

To restore data to NFCP500, first execute FcxSaveRetain-c to clear and hold the data, and then execute the FcxRestore command; Switch to online mode after recovery

A8 configuration NFCP500 exclusive features can be set through the Resource Configurator: Duolet function, CPU dual machine hot standby, NFCP502 3/4 Ethernet port, SD card, SNTP server, NFJT100 migration I/O definition

A9 Download Control Application Logic Designer R4 Open Project → Compile → Offline Download to Target Device

A10 executes APC (dual machine hot standby scenario) by inserting the standby side CPU module (of the same model and software version) → the resource configurator starts APC (manually executed when automatic start is disabled)

（2） Mode 2: Pre migration verification of internal equipment+on-site replacement

Applicable scenarios: sensitive on-site downtime, complex configuration (including field bus/Duolet applications), and the need to troubleshoot issues in advance

Core process (divided into three stages)

Stage 1: On site preparation (3 steps)

Step operation content output

B1 requires R4.20+tools to be installed on both the on-site and internal engineering PCs for obtaining conversion tools

B2 Save NFCP100 Keep data in the same mode Step A2 Keep data file

B3 backup NFCP100 data in the same mode, A3 step "Backup" folder

Stage 2: Internal device verification (7 steps)

Key points for verifying the operation content of steps

B4 Convert backup files (NFJT100 skip) in the same mode. A4 Step: Convert the "BackUP" folder after the conversion

B5 Configure internal NFCP500 new device with IP, switch to maintenance mode device ready (maintenance mode)

B6 restores data to internal NFCP500 in the same mode. A7 steps successfully restore data without any errors

B7 configuration exclusive functions in the same mode, A8 step function configuration takes effect

B8 download control application in the same mode. A9 steps: successful application download

B9 Verification Function Hardware (Communication, Dual Machine Hot Standby), Control Application Running Normal Verification Report

B10 optional: Backup internal NFCP500 data by executing the FcxBackup command, archive the verified configuration, and internally verify the backup file

Stage 3: On site replacement (steps 4-6)

Scenario step operation content

Internal and on-site I/O configurations are different B11-B16 B11: replace CPU module; B12: Switch maintenance mode; B13: Data recovery; B14: Configure exclusive functions; B15: Download applications; B16: Execute APC (dual machine)

Internal and on-site I/O configurations are the same C11-C14 C11: Save internal NFCP500 to maintain data; C12: Backup internal device data; C13: Replace CPU module; C14: Execute APC (dual machine)

Special Configuration Migration Adaptation

（1） Field bus definition migration (NFLF111/NFLP121/NFLC121 modules)