background image

 

< Appendix 3 Field bus Definition> 

31

 

 

 

 

TI 34P02K71-01E  3rd Edition: Aug. 28, 2017-00 

 

Appendix 3  Field bus Definition 

This chapter describes the work in the case of an autonomous controller 

NFCP100 were using the field bus (NFLF111, NFLP121, NFLC121 

communication module). 

The field bus definition information must be transferred from the engineering 

PC for NFCP100 to the engineering PC for NFCP500. 

TIP 

If you have used the R2.20 previous FF engineering tool, conversion is required from the FF engine 
tool to FF configurator. It offers a tool to support this conversion. After the conversion, you must check 
the operation of the field bus. 
For details, refer to "STARDOM FOUNDATION fieldbus System Migration Guide", TI 34P02Q55-01E. 

 

The field bus definition information CF/DD files for FOUNDATION fieldbus, GSD files for 

PROFIBUS or EDS files for CANopen, must be copied and imported from the 

engineering PC for NFCP100 to the engineering PC for NFCP500. 

SEE ALSO 

For how to copy CF/DD files for FOUNDATION fieldbus, refer to “5.8 Copying Fieldbus Associated 
Files”, IM 34P02Q51-02E. 
For CF/DD files, refer to “Items obtained from the device vendor” of “B1.2 Preparation for 
Engineering”, TI 34P02Q51-02E. 

For how to register GSD files for PROFIBUS, refer to “3.3.3 Registering GSD Files”, IM 
34P02Q57-01E. 

For how to register EDS files for CANopen, refer to “3.3.1 Registering Slave Devices”, IM 
34P02Q58-01E. 

 

If you want to engineering in a new PC for the NFCP500, export the definition 

information by resources configurator on the original PC, and then import this definition 

information by resources configurator on the new PC. 
If you upgrade the PC for NFCP100 to for NFCP500, export and import it does not need, 

because the definition information of the field bus is in the PC

●  Step 1: Export of definition information 

Originally a PC that had done the engineering of NFCP100, and export the resource 

configurator connected to the NFCP100. 

●  Step 2: Import of definition information 

In a new PC to perform the engineering of NFCP500, connect the resource configurator 

to the NFCP100, and import the file of Step1.

 

●  Step 3: Download of definition information 

In a new PC to perform the engineering of NFCP500, connect the resource configurator 

connected to the NFCP100, and download the file of Step1. 

 

Summary of Contents for Stardom FCJ

Page 1: ...TI 34P02K71 01E 4th Edition Jun 6 2018 Technical Information TI 34P02K71 01E STARDOM FCN 100 FCJ Migration...

Page 2: ...Blank Page...

Page 3: ...ke of simplicity this manual uses the least terminologies and the most basic functions For more details on functions and specifications please refer to other available documentation IM TI GS or online...

Page 4: ...Migrating the Control Application 5 2 Migrating on the target device directly 7 3 Migrating in house equipment in advance 15 Appendix 1 FCN FCJ and development tools 29 Appendix 2 Sample Libraries 30...

Page 5: ...the command operation on the personal computer Next step migrate the control application for the NFCP100 project on the Logic Designer to for the NFCP501 NFCP502 And download to the NFCP501 NFCP502 F...

Page 6: ...ked up from NFJT100 Re set IO setting by the resource configurator Re set DUONUS PRP by the maintenance page Retain saved file can be restored without conversion FcxBackup Command This command backs u...

Page 7: ...mmand FcxRestore Host name or IP address Host name or IP address Host name or IP address of the NFCP501 NFCP502 E g FcxRestore 192 168 0 1 TIP When restoring the file backed up from the NFCP100 and co...

Page 8: ...figuration example If you specify C temp to the destination folder of the conversion tool C temp NFCP500 Current Folder FcxBackup exe Backup command FcxConvert exe Convert command FcxRestore exe Resto...

Page 9: ...g itself If the PLC type is IPC_32 or IPC_33 re create the resource with IPC_40 and re compile Expanding the retain data area Extend function If the PLC type is IPC_40 re create the resource with FCFX...

Page 10: ...extension units and NFLF111 NFLP121 NFLC121 device label extended version of FCX_B 2 If the PLC type is IPC_40 the project for NFCP100 can be used by re compiling without changing itself If the PLC t...

Page 11: ...grate from NFCP100 to NFCP500 Except for the noted items it is also true for NFJT100 Migration Environment The Tools for NFCP500 are required on the engineering PC Logic Designer R4 20 or later Resour...

Page 12: ...ller as the key If field bus communication modules are used it requires advance preparation For detail refer to Appendix 3 Field bus Definition Figure Flowchart of migration Step A1 Obtaining conversi...

Page 13: ...oring unzipped files is C temp the following files will be created in that Folder C temp NFCP500 FcxBackup exe C temp NFCP500 FcxRestore exe C temp NFCP500 FcxConvert exe C temp FCXTOOL FcxSaveRetain...

Page 14: ...skip this step Step A4 Converting the backup files except NFJT100 1 In the command prompt window type FcxConvert t new CPU type i Source folder o Destination folder and press the Enter key Some files...

Page 15: ...ame or IP address and press the Enter key The command with c option only clears the retain data on the SRAM and does not save the retain data e g C temp NFCP500 FcxSaveRetain c 192 168 0 1 4 In the co...

Page 16: ...load it Duolet function If necessary CPU duplex configuration If necessary Ethernet port No 3 and No 4 for NFCP502 If necessary SD card If necessary I O definition migrating from NFJT100 only 2 Set so...

Page 17: ...Logic Designer R4 The projects in the format of R3 or earlier are converted automatically to R4 format TIP The project of R4 format can t be opened in the R1 R2 R3 Logic Designer 3 If the PLC type is...

Page 18: ...oad the boot project and the source files as needed Step A10 Executing APC Duplex CPU only 1 After confirming the connection of Ethernet cable and the RS 233 C cable insert the other one CPU module fo...

Page 19: ...s operation check in house to NFCP500 in the field 2 In Step B1 to B10 and C11 to C14 describes the following procedure Prepare the same I O configuration as the target device as an in house equipment...

Page 20: ...of the controller as the key If field bus communication modules are used it requires advance preparation For detail refer to Appendix 3 Field bus Definition Step B1 Obtaining conversion tools Step B2...

Page 21: ...maintenance mode Step B13 Restoring the NFCP500 Step B14 Setting each function for NFCP500 Step B15 Downloading the control application to the NFCP500 B11 Step B16 Executing APC Duplex CPU only On sit...

Page 22: ...fied folder for storing unzipped files is C temp the following files will be created in that folder C temp NFCP500 FcxBackup exe C temp NFCP500 FcxRestore exe C temp NFCP500 FcxConvert exe C temp FCXT...

Page 23: ...In the command prompt window change the current directory to the folder containing the extracted conversion tools in Step B1 Supposing that the conversion tools has been extracted to the folder C tem...

Page 24: ...to maintenance mode on the NFCP500 1 Run the Web browser and open the STARDOM Maintenance Page on the NFCP501 NFCP502 2 Select Maintenance Menu The FCX Maintenance Menu is displayed 3 Select Reboot Th...

Page 25: ...the FCN 500 Please use the CPU module to the required licenses are bundled Step B8 Setting each function for the NFCP500 1 Set some settings for new function or additional configuration by the resourc...

Page 26: ...projects in the format of R3 or earlier are converted automatically to R4 format TIP The project of R4 format can t be opened in the R1 R2 R3 Logic Designer 3 If the PLC type is defined in IPC_32 IPC...

Page 27: ...ownload the boot project and the source files as needed Step B10 Checking the operation of NFCP500 Hardware operation communication function CPU duplex configuration The operation of the control appli...

Page 28: ...ces configurator Step B12 Switching to maintenance mode on the NFCP500 1 Run the Web browser and open the STARDOM Maintenance Page on the NFCP501 NFCP502 2 Select Maintenance Menu The FCX Maintenance...

Page 29: ...the FCN 500 Please use the CPU module to the required licenses are bundled Step B14 Setting each function for the NFCP500 1 Set some settings for new function or additional configuration by the resou...

Page 30: ...t project and the source files as needed IMPORTANT The retain data that changed or added to in house equipment re set it in the field Step B16 Executing APC Duplex CPU only 1 After confirming the conn...

Page 31: ...e SAVE button is not displayed in the maintenance mode Step C12 Backing up the NFCP500 1 In the command prompt window change the current directory to the folder containing the extracted conversion too...

Page 32: ...same Ethernet port 1 or 2 before the exchange 3 Insert the NFCP501 NFCP502 using in house equipment to the base module In the case of CPU duplex configuration insert only the control side CPU module...

Page 33: ...N FCJ autonomous controller with basic software R3 and R4 FCN FCJ Autonomous controller R4 Logic Designer R4 Resource Configurator FCN FCJ Basic software R1 R2 R3 X R4 X When opened in logic designer...

Page 34: ...obal member rtu engsample index htm E g libraly folder C YOKOGAWA FCN FCJ LogicDesigner Libraries Step 2 Adding Sample Libraries 1 Open the library compressed project file in the Logic Designer and co...

Page 35: ...s Associated Files IM 34P02Q51 02E For CF DD files refer to Items obtained from the device vendor of B1 2 Preparation for Engineering TI 34P02Q51 02E For how to register GSD files for PROFIBUS refer t...

Page 36: ...R4 02 with FCN 500 project migration work is required Migrate the project according to the following procedure 1 Change the CallJavac bat file in the project folder of the Duolet application to a diff...

Page 37: ...Application Jun 2018 4th Edition R4 20 or later Reviced Added processor type FCX_C Changed obtain procedure of tool Denotes the release version of the software corresponding to the contents of the te...

Reviews: