Core logic: The field bus definition is bound to the engineering PC and needs to be migrated from the source device engineering PC to the target device engineering PC
operating steps
File preparation: Copy the configuration file from the source PC (FOUNDATION field bus: CF/DD file; PROFIBUS: GSD file; CANopen: EDS file);
Define migration:
Same PC upgrade: No need to export/import, definition information is already stored on the PC;
New PC project: Source PC → Resource Configurator export definition → New PC import definition → Download to target device;
Special adaptation: When using FF engineering tools before R2.20, it is necessary to first convert them to FF Configurator format (refer to TI 34P02Q55-01E).
(2) Duolet (Java) application migration
1. System file editing
In the converted DUONUS.PRP file, a "#" comment will be added before JavaStart and AdditionalClassPath. After recovery, the "#" should be removed to activate the application;
Editor's reference: "B 2.4.2 Editing System Setting Files" in IM 34P02Q01-01E.
2. Project migration
Step operation content
1. Rename CallJavac.bat in the project folder to CallJavac.bat.old, and Ftp2Fcx.bat to Ftp2Fcx.bat.old
Copy CallJavac.bat, CallJavac_Fcn500.bat, and Ftp2Fcx.bat from the "Project Template" directory of the tool installation directory to the project folder
3. Edit Ftp2Fcx.bat, configure the target device IP, package name included in the JAR package, and JAR file name
Execute CallJavac.bat or CallJavac_Fcn500.bat to confirm the generation of the Duolet application
5. Note: The deprecated method of IEC control data access class cannot be used for FCN-500
