5.1.4 Precautions of Migrating Testing from In-house
Equipment to Target Equipment
Debugging is sometimes started on in-house test equipment and then migrated to
the target equipment halfway through function test. We describe two migration
scenarios below.
● If CPU Module of In-house Equipment Are Used before Migration
In this migration scenario, debugging started using the CPU module of in-house
equipment is to be migrated to the target equipment upon delivery of its CPU
module.
Firstly, migrate the information stored on the CPU module of the in-house equipment
to the target CPU module using the following steps:
1. Save retain data specified on in-house equipment to its CPU module.
2. Execute the FcxBackup command to save data stored on the CPU module of the
in-house equipment to a PC.
4. Define the IP address on the target CPU module.
5. Execute the FcxRestore command to migrate the data of the CPU module of the
in-house equipment saved on the PC earlier to the target system card.
• Resource Configurator settings
Configuration data defined using Resource Configurator is saved in the CPU
module on-board flash memory. However, if the I/O module configuration is
different between the in-house equipment and target equipment, I/O modules
need to be reconfigured and device labels redefined for the target equipment.
• Items saved by FcxBackup command
The list of items to be saved by FcxBackup command is defined in a file named
“backuplist.txt” stored in the same folder as the “FcxBackup.exe” executable file.
The default backuplist.txt file list covers IEC 61131-3 language control
applications but does not include files added by Duolet applications. Read
“README.TXT” and edit the “backuplist.txt” file accordingly to add to or modify
the list of items to be saved by FcxBackup command as required.
To Next Page
Loading...
Need help?
General
