subject

Contents

Server configuration file

Server setting files developed with the Ver5 FA series do not require any special migration work. They can be opened as is in Ver6 FA-Server.

However, please note the following points:

1)In FA-Server version 6 and later, Daily/Monthly/Yearly Report actions have been discontinued. You cannot migrate the Daily/Monthly/Yearly Report actions from previous versions as they are.For information on migrating actions, please see “Features discontinued with the upgrade to FA-Server6” below.

2)Some communication drivers are limited to 32-bit operation from Ver6 onwards. If you want to continue using these drivers, please install and use the 32-bit version. For details, please refer to "Functions discontinued with the upgrade to FA-Server6" below.

3)In addition, the discontinued functions described below in "Functions discontinued by the upgrade to FA-Server6" cannot be migrated to Ver6.

Other data files etc.

Starting with Ver6, all functions are now officially compatible with Unicode.

Due to this change, the various data files (such as CSV files) that each function saves externally have been changed from the ANSI format of the previous version to the UTF-8 format.

In addition, data files in ANSI format generated by older versions and master files for each action (for example, historical data (CSV)) can be read as is without any special conversion work (when overwriting using the functions of this package, they will be automatically converted to UTF-8 and saved).

Therefore, if you migrate a monitoring system that was running on Ver5 to Ver6, various data files will be saved in UTF-8 format, so you will not be able to revert back to Ver5. When migrating your system, we strongly recommend that you always keep backup data in case you need to revert back to Ver5.

Integration with external systems

With support for Unicode,Files output from this package (such as CSV files) are all saved in UTF-8 format from Ver6 onwards. If some sort of functional linkage has been built, such as an external system importing data files output by this system, some kind of correction may be required in the part of the external system that imports the data.

Furthermore, when loading files generated by external systems with this package, the files can be loaded without any problems even if they are saved in ANSI format.

All functions are now fully Unicode-compatible in Ver6 and later. Data files that each function saves externally (such as CSV files) will be in UTF-8 format instead of the ANSI format of previous versions.

There is no need to perform any special conversion work for ANSI format data files and master files for each action that were generated in the previous version, and they can be directly loaded into the new version (when loading, the file type is determined, and if it is in ANSI format, it will be loaded in ANSI format. When saving over a file, it will automatically be converted to UTF-8 and saved).

case

What to migrate

How to migrate

Case 1
 

If logging was performed using the logger action of FA-Studio5 (or FA-Logger5)

1)Start FA-Server6, open the setting file created with FA-Studio5 (or FA-Logger5), perform Set up the public folder, and then go online.

2)Start FA-Client6 and configure the pen settings on the trend graph screen.
 

Case 2

When external data logged by a system other than ours is imported using the Historical data server action defined in FA-Trend5

1)Start FA-Server6, open the configuration file created in FA-Trend5, Set up the public folder, and then go online.

2)Start FA-Client6 and configure the pen settings on the trend graph screen.

Case 3

In the case of a system that combines Case 1 and Case 2

1)Start FA-Server6, open the setting file created in FA-Studio5 (or FA-Logger5), and perform Set up the public folder.

2)The Historical data server action settings used in FA-Trend5 will be added (migrated) to FA-Server6 and made online.

3)Start FA-Client6 and configure the pen settings on the trend graph screen.

What to migrate

How to migrate

If you were using FA-Report5

In FA-Server Ver.6 and later, the Daily/Monthly/Yearly Report actions used in FA-Report5 have been discontinued. You cannot migrate the Daily/Monthly/Yearly Report actions from previous versions as they are.For information on migrating actions, please see “Features discontinued with the upgrade to FA-Server6” below.

action

Action

The "Daily/Monthly/Yearly Report Actions" provided in versions prior to Ver. 5 have been discontinued due to their integration into "Summary Actions".

If you have used the Daily/Monthly/Yearly Report action in FA-Studio (FA-Report) prior to Ver. 5, you will no longer be able to use it in FA-Server6 or later..

There are the following methods to migrate a system operated with the old version of Daily/Monthly/Yearly Report action to Ver6.

1)Rebuild system with summary action for FA-Server6

This is a method to replace the logging/report aggregation function built with the old version of the Daily/Monthly/Yearly Report action with the new version of the summary action. In this case, it is necessary to create a new aggregation function using the summary action.

Furthermore, because the data formats saved by Daily/Monthly/Yearly Report actions and summary actions are not compatible, it is not possible to migrate the history data saved by the previous version of Daily/Monthly/Yearly Report actions as is.

2)Use the 32-bit version of FA-Panel6

This is a method for migrating your system to "FA-Panel6", a higher-end package product of FA-Server. The 32-bit version of FA-Panel6 has Daily/Monthly/Yearly Report actions remaining for upward compatibility, and can still be operated. Server setting files built with FA-Server5 can be loaded and executed as is by FA-Panel6's PanelServer. When migrating using this method, historical data saved in the old system can be migrated as is.

However, due to the discontinuation of the "Report View" below, you will need to create a new client screen for displaying report data as a client application that runs on FA-Panel6's PanelBrowser. In this case, you will need to purchase FA-Panel6 instead of FA-Server6 (note that when creating a report screen with FA-Panel6's PanelBrowser, a sample screen that can be used in almost the same form is provided).

View

Report View

The FA-Report report view has been discontinued and replaced with the FA-Client report screen. Note that the FA-Client report screen is built as a screen dedicated to summary actions and cannot be connected to Daily/Monthly/Yearly Report actions.

Log Data Graph View

The FA-Trend log data view has been discontinued and replaced with the FA-Client trend graph screen.

Communication features

Communication Driver

The following communication drivers have been discontinued:

•Yokogawa Electric FA-M3 AT compatible CPU module

•Yokogawa Electric FA-M3 Ethernet (email) equivalent to LE11-0T

•SMC Thermo-con RS-232C HEC105W/HEC205W equivalent

•Microsoft Office(Excel/Word/Powerpoint)

However, from Rev11 onwards, the Microsoft Office(Excel) driver is available.

SuiteLink

FA-Server for Wonderware has been discontinued. If you are using SuiteLink with FA-Server for Wonderware in an older version environment, please use another interface such as OPC to connect in version 6 or later.

Communication features

Communication Driver

The following drivers only work in 32-bit version.

•Mitsubishi Private Protocol Communication Driver
* CPU direct connection, MELSECNET/H board, CC-Link board, etc.