[PDF]General Specifications - Rackcdn.comc15181565.r65.cf2.rackcdn.com/GS34P02P53-01E_1.pdfGENERAL. Logging Portfolio (InfoWell) is a software package...
0 downloads
195 Views
1MB Size
<> <>
STARDOM Logging Portfolio (InfoWell)
General Specifications GS 34P02P53-01E
GENERAL
Logging Portfolio (InfoWell) is a software package that runs in an autonomous controller FCN/FCJ and that is designed to log process data. An autonomous controller FCN/FCJ is a controller that is equipped with both a control function equivalent to that of a programmable logic controller (PLC) and an information processing and transmission function equivalent to that of a PC. InfoWell is a group of packages that is designed to perform these information processing and transmission functions through a simple setup procedure. Logging Portfolio provides a logging function that is indispensable for managing the utilities and equipment. It collects data from the control application in an autonomous controller FCN/FCJ in various forms ideal for use by the system, and saves it in a logging file (in CSV format). This logging file can be viewed in various forms (trend view, table format view, etc.) from the Web browser via a network. The logging file can also be sent by e-mail. Use of software for a PC that is included in the package allows for the acquisition of logging files periodically from the PC via a network for further use. Logging Viewer View data
PC
(Offline)
Logging file
Logging file
F01E.ai
Figure Logging Function
Rich View Functions and E-mail Transmission Logged data can be viewed on a Web browser in a variety of forms such as trend view and table format view. Logged data (Simple report) can also be transmitted by e-mail. Advanced Use of Data A logging file collector running on a PC allows for periodically collecting logging files (in CSV format) on a PC. This makes it simple to analyze data using MS Excel, for example. #APPNAME #FILEREV #LOGTYPE #TIMEZONE #TITLE #DATE #DATA #DATA #VAR #LABEL #UNITS #TYPE 080525 13:00:01 080525 13:00:02 ………
080525 14:00:00 #MINIMUM #MAXIMUM #AVERAGE #TOTAL
SD-DLG
0 DATA_HC GMT+9 Log File Title 080525 13:00 Main.PI100_HI Main.LI100 Main.PI100 Vessel Pressure KPa REAL 123.45 1234.56
Pressure HI Limit Initial Level Main.PI200 Outlet Pressure KPa REAL 123.46 12.35
2300.00 2345.67 Main.FI100 Inlet Flow m3/min REAL 34.5 45.6
KPa mm Main.FI200 Outlet Flow m3/min REAL 12.34 *** ………
FCN／FCJ
Save data
Rich Data Logging Functions In addition to a basic function to periodically log and save data in a logging file, there are various functions such as a batch logging for recipe management, snapshot logging for reducing total amount of data, SOE ( Sequence of Events) logging for collecting data before and after an event such as event is detected, or message logging function for recording failures and recovery of devices and controllers. The most suitable recording method can be selected according to the purpose.
………
Logging function
Simple Logging Configuration A simple setup makes it possible to log the data of the control application.
………
Collect data
Simple Configuration without PC A highly reliable logging function can be implemented at low cost without using a PC. There is no need to maintain a dedicated PC running 24 hours a day. Moreover, there is no need of communication between FCN/FCJ and PC, although a large amount of data can be logged at a high speed.
………
Control application
Collector
ata
(Online)
td
View data
llec
Co
Ethernet
FEATURES
23.4 *** 23.4 45.6 35.6 128160.0
12.34 12.34 12.34 44424.00
12.34 12.34 1234.56 567.40
1234.56 12.35 1234.56 567.80
F02E.ai
Figure Example of Logging File
Yokogawa Electric Corporation 2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan Tel.: 81-422-52-5616 URL: http://www.stardom.biz
GS 34P02P53-01E ©Copyright Apr. 2008(YK) 12th Edition Aug. 9, 2012(YK)
2
<> <>
FUNCTION OVERVIEW
Data Logging
Logging Portfolio (InfoWell) provides the following functions. • Logging function • Logging File View function • Logging File Collection function • Logging File (Simple report) Transmission (E-mail) function • Logging Configuration function
LOGGING FUNCTION
The logging function has the following functions. • Data Logging • SOE ( Sequence of Events) Logging • Message Logging
Control application Data
FCN/FCJ Logging function
Collect data
Block
Blockデータ Block データ Data
40 items
40 40 items
Save
There are the following types of data logging. Table Data Logging
Logging type
Hourly logging
F03E.ai
Figure Data Logging Function Note: The logging type can be set on a block basis. Note: Logging files are created on a block basis. Note: One logging file is created on each closing process.
*2: *3:
*4:
*5:
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
Closing timing
1 to 60 1 to 60 Every seconds minutes hour (*1) (*3) (*2)
1 to 60 Every minutes day (*2) Batch 1 to 60 1 to 60 start/ Batch logging seconds minutes stop (*1) (*3) (*2) switch Every hour or Continuous every Snapshot Trigger day logging Closing Triggered trigger
Daily logging
*1:
Logging file
Periodic data collection High Low speed speed (*5)
-
Simple report (*4) Daily, monthly, yearly report Monthly, yearly report Daily, monthly, yearly report -
Any of the fixed values (1, 2, 5, 10, 15, 30, and 60 seconds) can be set. Any of the fixed values (1, 2, 5, 10, 15, 30, and 60 minutes) can be set. To collect data, a program organization unit (POU) for logging is required when programming a control application. Periodic collection depends on the scan period of the task. A simple report, including daily, monthly and yearly report, is a CSV format file consisting of closing values (maximum, minimum, average and total). Not supported by FCN-RTU (NFCP050) style S1.
GS 34P02P53-01E Aug. 9, 2012-00
3
<> <> Hourly Logging Hourly logging collects data in a specified collection period, closes processing once every hour, and creates an hourly logging file. Periodic data collection options are high speed (1 to 60-second period) or low speed (1 to 60-minute period). The closing processing of hourly logging calculates the maximum, minimum, average, and total values and saves them along with the collected data in the logging file. The saved logging file is compressed in Zip format. Simple reports (daily report, monthly report, or yearly report) can also be created based on the collected data. Collect data at a specified collection interval
Daily Logging Daily logging collects data in a specified collection period (1- to 60-minute period), closes processing once every day and creates a daily logging file. The closing processing of daily logging calculates the maximum, minimum, average, and total values and saves them along with the collected data in a logging file. The saved logging file is compressed in Zip format. Simple reports (monthly report and yearly report) can also be created based on the collected data. Collect data at a specified collection interval
Close processing
Collect data at a specified collection interval
Close processing
Close processing
Daily logging file
Daily logging file
Create simple report
Close processing
Hourly logging file
Collect data at a specified collection interval
Monthly report
Hourly logging file
Create simple report
Yearly Report
Daily report
F05E.ai
Figure Operation Example of Daily Logging (with a Simple Report)
Monthly report
Yearly Report F04E.ai
Figure Operation Example of Hourly Logging (with a Simple Report)
#APPNAME #FILEREV #LOGTYPE #TIMEZONE #TITLE #DATE #DATA #DATA #VAR #LABEL #UNITS #TYPE #ON_LABEL #OFF_LABEL 071220 13:00:01 071220 13:00:02
0 DATA_HC GMT+9 Log File Title 071220 13:00 Main.PI100 Main.LI100 Main.PI100 Vessel Pressure KPa REAL
123.45 1234.56
Data collection time Vessel Pressure Initial Level Main.PI200 Outlet Pressure KPa REAL
1523.23 2345.67 Main.FI100 Inlet Flow m3/min REAL
123.456 12.3456
34.5 45.6 ***
Main.PUMP1 Inlet pump
12.34 12.34 12.34 44424
STOP
Header information (labels)
123.45
Collected data
………
23.4 *** 23.4 45.6 35.6 128160
*** ………
Data (up to 40 items)
Header information (parameters)
Main.TI100 Vessel Temp DegC REAL
BOOL RUN STOP 12.34 RUN RUN
………
1234.56 12.3456 1234.56 567.8
KPa mm Main.FI200 Outlet Flow m3/min REAL
………
12.34 12.34 1234.56 567.4
Header information (file attributes)
Start time to collect data
………
………
………
071220 14:00:00 #MINIMUM #MAXIMUM #AVERAGE #TOTAL
SD-DLG
23 37 4
123.45 23.45 432.1 234.5
Footer information (closed logging data) F06E.ai
Figure File Example of Hourly Logging
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
GS 34P02P53-01E Nov. 11, 2008-00
4
<> <> #VAR #LABEL #UNITS #TYPE 071220 13:00:01 071220 13:00:02
Main.PI100 Vessel Pressure KPa REAL 123.45 1234.56
Main.PI200
Outlet Pressure Hourly logging KPa REAL
123.456 12.3456
Main.FI100 Inlet Flow m3/min REAL
REAL
REAL 128000 128160
123.456 12.3456
12.34
REAL 3093880 3080000
1234.56
12.34 12.34 1234.56 567.4
1234.56 12.3456 1234.56 567.8
3080880 ………
080101 00:00:00 #MINIMUM #MAXIMUM #AVERAGE #TOTAL
123.456 12.3456
………
………
………
129200 128000 129200 128370 3080880
REAL
………
071221 00:00:00
………
1234.56 12.3456 1234.56 567.8
Main.FI100
………
128160
………
1234.56
Main.PI200
Outlet Pressure Inlet Flow Simple monthly report KPa m3/min
Close and compile the simple daily reports and record the results in a simple monthly report
………
………
………
12.34 12.34 1234.56 567.4
Main.PI100 Vessel Pressure KPa REAL 123.45 1234.56
………
12.34
#VAR #LABEL #UNITS #TYPE 071202 00:00:00 071203 00:00:00
………
071221 00:00:00 #MINIMUM #MAXIMUM #AVERAGE #TOTAL
Main.FI100
………
23.4 23.4 45.6 35.6 128160
………
1234.56 12.3456 1234.56 567.8
Main.PI200
Outlet Pressure Inlet Flow Simple daily report m3/min KPa
………
071220 14:00:00
………
12.34 12.34 1234.56 567.4
12.3456 ………
………
………
071220 14:00:00 #MINIMUM #MAXIMUM #AVERAGE #TOTAL
1234.56
………
071220 13:00:30
Main.PI100 Vessel Pressure KPa REAL 123.45 1234.56
………
45.6
Close the hourly logging, compile the collected data, and record the results in a simple daily report ………
………
34.5 45.6
#VAR #LABEL #UNITS #TYPE 071220 01:00:00 071220 02:00:00
3080880 3080000 3093880 3085003 95635093
F07E.ai
Figure Example of Generating Simple Daily and Monthly Report
Batch Logging This function collects data in a specified collection period and saves it in the file while the batch start/stop switch (*1) is true. The periodic data collection options are either high speed (1- to 60-second period) or low speed (1- to 60-minute period). A simple report is not created. Note: Whenever the batch start/stop switch is true, a new file is created. *1: Batch start/stop switch This is a Boolean type variable of control application to specify the period to collect data. At the timing when the batch start/stop switch is changed from false to true (when starting data collection) or oppositely changed from true to false (when stopping data collection), data collection will also be executed. The interval between True and False of Batch start/stop switch must be one minute or longer. :True
Batch start/stop switch
:False
Collect data at a specified collection interval
Close processing
Batch logging file F08E.ai
Figure Operation Example of Batch Logging
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
GS 34P02P53-01E Nov. 11, 2008-00
5
<> <> Snapshot Logging This function collects data and saves it in a file at the timing when a data collection trigger becomes True. There are two types, Continuous and Trigger, in accordance with the logging closing method. • Snapshot Logging (Continuous) This function performs the closing processing at a specified time and creates a logging file. A simple report (daily report, monthly report, or yearly report) can also be created. Data collection trigger
:True :False
Collect data
Collect data
Close processing
Snapshot logging file
Create simple report
Note: After the closing processing is performed, the next data collection trigger creates a new file and starts logging.
:True
Close trigger
Close processing
Snapshot logging file
• Snapshot Logging (Trigger) This function generates a file when the first data collection trigger becomes True, and then ends the logging and saves the data in the file when a closing trigger becomes True. A simple report cannot be created.
:False
Data collection trigger
:True :False
Daily report
Collect data
Monthly report
Close processing Yearly Report F09E.ai
Figure Example of Snapshot Logging (Continuous)
First trigger generates file
Snapshot logging file F10E.ai
Figure Operation Example of Snapshot Logging (Trigger) Note: Both the “data collection trigger” and “closing trigger” are Boolean type variables of control application.
SOE (Sequence of Events) Logging SOE (Sequence of Events) logging collects data at high speed before and after the detection of event such as failure and saves data in a file. A simple report is not created.
FCN/FCJ
Logging function
Collect data
Blodk Blodk Blodk items items Data
32items 32items 40 items
High speed data collection before and after Event Detection
Y
Data before event
Data after event
Event
Event detection
X
Event detection
Save
SOE Logging File
Data collection (600 data)
:True :False
SOE logging file
t F18E.ai
Figure SOE Logging Function
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
F19E.ai
Figure Operation Example of SOE Logging
GS 34P02P53-01E Nov. 11, 2008-00
6
<> <>
Message Logging This function saves FCN/FCJ messages in a continuous (one-minute) period in the file. The messages can also be filtered by the message number. #APPNAME #FILEREV #LOGTYPE #TIMEZONE #TITLE #DATE #TIME 080415 07:37:07.150 080415 07:37:11.250 080415 07:37:15.350 080415 07:37:19.450 080415 07:37:23.550 080415 07:37:27.650 080415 07:37:31.750 080415 07:37:35.850
SD-DLG 0 MSG GMT+9 Log File Title 071220 13:23 ID CATEGORY 1806 APPLICATION 1801 APPLICATION 1806 APPLICATION 1801 APPLICATION 9018 APPLICATION 9018 APPLICATION 9018 APPLICATION 9018 APPLICATION
TYPE EVENT EVENT EVENT EVENT ALARM ALARM ALARM ALARM
SOURCE MSG100.MSG_BLOCK_01.USRALM MSG100.MSG_BLOCK_01.USREVT MSG.MSG_BLOCK_01.USRALM MSG.MSG_BLOCK_01.USREVT TRIGGER.BATCH_MSG1 TRIGGER.BATCH_MSG2 TRIGGER.SNAP_MSG1 TRIGGER.SNAP_MSG2
MESSAGE MSG100.MSG_BLOCK_01.USR...... MSG100.MSG_BLOCK_01.USR...... MSG.MSG_BLOCK_01.USRALM...... MSG.MSG_BLOCK_01.USREVT...... TRIGGER.BATCH_MSG1 Batch...... TRIGGER.BATCH_MSG2 Batch...... TRIGGER.SNAP_MSG1 Writing...... TRIGGER.SNAP_MSG2 Closing......
Header information (labels)
Messages
………
………
………
………
………
………
080415 07:55:19.550 080415 07:55:23.650
Header information (file attributes)
1806 APPLICATION EVENT MSG100.MSG_BLOCK_01.USRALM MSG100.MSG_BLOCK_01.USR...... 1801 APPLICATION EVENT MSG100.MSG_BLOCK_01.USREVT MSG100.MSG_BLOCK_01.USR...... F11E.ai
Figure Example of Message Logging File
LOGGING FILE VIEW FUNCTION
LOGGING FILE COLLECTION FUNCTION
Logging files on FCN/FCJ are periodically collected on PC using logging file collection function. Collection can also be performed manually whenever necessary. The following methods are prepared for the logging file collection function. Select one of them for the intended purpose. • Logging File Collector It runs in the task tray while PC is logged on. • Logging File Collection Service It runs as a PC service even if PC is not logged on. PC
Logging File Collection
FCJ
View data
PC Coll
ct
ect
Colle
Logging file
Message View Function FCN/FCJ message logs that were collected can also be viewed in Logging Viewer in the same manner as viewing data. Logging Viewer
Logging file Ethernet
Logging File View Function Data collected by the logging function can be viewed in Logging Viewer on the Web browser (online view). Logging files not only in the FCN/FCJ but also those collected on the PC can be simply viewed using Logging Viewer (offline view). Trend View and Table Format View are available in Logging Viewer.
FCN
(Offline)
Logging file
Ethernet
View data (Online)
F13E.ai
Figure Logging File Collection Function FCN/FCJ
Collector
Logging file
t ec
ll Co
Logging file F12E.ai
Figure Viewing Logging File by Logging Viewer
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
GS 34P02P53-01E
Feb. 2, 2011-00
7
<> <>
LOGGING FILE TRANSMISSION (EMAIL) FUNCTION (*1) This function allows for transmitting logging files as attachments by e-mail.
E-mail server
Transmit e-mail
Mobile phone
PC
LOGGING CONFIGURATION FUNCTION
A Logging Configurator allows for configuring how to collect data. This tool has an online mode that allows for directly changing the configuration information in the FCN/FCJ and an offline mode that allows for downloading the configuration information to the FCN/FCJ after it is changed on the PC. PC
Logging configurator
Logging file transmission function
Ethernet
Ethernet
Logging file
Logging configuration data
FCN/FCJ
FCN/FCJ
F14E.ai
PC Logging configuration data
Logging configurator d
Note: • An e-mail server is required on the intranet to transmit e-mail. • Use E-mail Application Portfolio (InfoWell) to transmit FCN/FCJ messages and alarms by e-mail. The Logging File Transmission (Email) Function and E-mail Application Portfolio (InfoWell) can be applied simultaneously. • The logging files that can be transmitted are simple reports (daily report, monthly report, and yearly report).
loa
Figure Logging File Transmission (E-mail) Function
F15E.ai
Figure Logging Configurator (Online)
Ethernet
wn
Not supported by FCN-RTU (NFCP050) style S1.
Do
Collected data
*1:
Web browser
Logging configuration data
FCN/FCJ F16E.ai
Figure Logging Configurator (Offline) Note: When using the logging configurator offline, the tool is required to be installed in the PC.
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
GS 34P02P53-01E
Feb. 2, 2011-00
8
<> <>
DATA LOGGING FUNCTION SPECIFICATIONS Table Data Logging Function Specifications Specifications
Item
Data Logging / SOELogging
Data to be collected
FCN/FCJ control application variables
Number of items
40 items/block
Number of blocks Logging block start/stop trigger Amount of data to be saved File format Total logging file size Logging block size Number of files
Message Logging FCN/FCJ message -
FCN, FCJ (*10)
25 blocks (*2) (10 blocks in case of high-speed data collection) (*8)
FCN-RTU
16 blocks (*11) (*12)
2 blocks
BOOL-type control application variable (*1) (*9) FCN, FCJ (*10)
60,000 items/min. (*3)
FCN-RTU
30,000 items/min. (*13)
CSV form (*4) Limited by the free space on the FCN/FCJ system card (500 MB max) or flash memory on FCN-RTU (80 MB max) (*14) Specify the maximum data size on logging block basis. The specified values must be such that the sum of all logging block sizes does not exceed the total logging file size. (*5)(*6) 400 files per logging (*7)
Note: When there is possibility of power interruption in the electric supply to FCN/FCJ, please connect an uninterruptible power supply system (UPS). *1: Logging for a logging block can be started or stopped from a control application by specifying a variable as a block start/ stop trigger. If no trigger is specified, the logging block is always activated (in RUN status). *2: This represents the total number of blocks for the data logging function and SOE logging function. *3: Collecting this amount of data is equivalent to increase in CPU load by 25 % to 30 %. CPU load is increased when e-mails are sent, simple reports are created and messages are logged. *4: When closing processing is performed, the logging file is compressed into Zip format, normally to between 10% and 50% of the original file size. *5: The oldest file is removed when collected data for a logging block exceeds the specified logging block size, even if the number of files accumulated in a logging block does not exceed 400. *6: In case of hourly logging (for up to 40 data items and in a collection period of 1 second), the maximum size of one file is approximately 1.7 MB. The file is compressed to the one-third compared to the size of the original file in Zip format, except for a logging file for which data is currently being collected. When a 100 MB area is allocated, approximately 170 files (for one week) can be logged. *7: Files are deleted from the oldest when the number of files accumulated in a logging block exceeds 400, even if collected data for a logging block does not exceeds the specified logging block size. *8: This represents the total number of blocks for the high-speed data collection, namely hourly logging(high-speed), batch logging(high-speed) and SOE logging. *9: The interval between True and False of start/stop trigger of logging block must be one minute or longer. *10: Except FCN-RTU. *11: Maximum of the total number of blocks for high-speed data collection, low-speed data collection, and SOE logging is 16. Maximum of the total number of blocks for high-speed data collection and SOE logging is 5. *12: FCN-RTU can be used only with low-speed data collection function. High-speed data collection and SOE logging function are not supported. *13: 8,000 items/min. in case of FCN-RTU (NFCP050) style S1 *14: 16 MB max in case of FCN-RTU (NFCP050) style S1
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
GS 34P02P53-01E Aug. 9, 2012-00
9
<> <> Table Detailed Specifications of Hourly and Daily Logging Functions Hourly logging Daily logging High speed Low speed collection collection Periodic 1, 2, 5, 10, 15, 30, 1, 2, 5, 15, 30, 60 collection 60 second(s) minute(s) Data to be POU for logging FCN/FCJ control collected data (*1) application variables (*2) Closing timing Fixed period Closing processing 1 hour 1 day period Closing time Specify in minutes Specify in hours Select from Items to be “None,” generated at “Minimum, maximum, average,” closing time “Minimum, maximum, average, total.” Select from Select from “None,” “None,” Simple report “Daily report,” “Monthly report,” (*3) “Daily and monthly report,” “Monthly and “Daily, monthly, and yearly yearly report.” report.” Item
*1: *2:
*3:
The data types that can be connected to the POU for logging data are CData_REAL, REAL, CData_INT, INT, and BOOL. FCN/FCJ control application variables with an OPC check. The data types of variables that can be collected are CData_REAL, CData_INT, REAL, LREAL, INT, SINT, UNIT, USINT, DINT, UDINT, BOOL, and STRING. Simple reports can be transmitted by e-mail. (E-mail function is not supported by FCN-RTU (NFCP050) style S1.)
Table Detailed Specifications of Batch Logging Function Batch logging High speed Low speed collection collection 1, 2, 5, 10, 15, 30, 1, 2, 5, 10, 15, 30, Periodic collection 60 second(s) 60 minute(s) FCN/FCJ control POU for logging Data to be collected application (*1) variables (*2) Closing processing When data collection is finished Select from Items to be “None,” generated at “Minimum, maximum, average,” closing time “Minimum, maximum, average, total” Simple report Unavailable Item
*1: *2:
Table Detailed Specifications of Snapshot Logging Function Item Periodic collection Data to be collected
Snapshot logging Continuous collection Trigger More than 1 minute for the data collection trigger (*3) interval FCN/FCJ control application variables (*1) Closing trigger (*3) (*4)
Close timing
Fixed period
Closing processing period
1 hour
1 day
-
Closing time
Specify in minutes
Specify in hours
-
Simple report (*2)
Select from “None,” “Daily report,” “Daily and monthly report,” and “Daily, monthly, and yearly report.”
Select from “None,” “Monthly report,” and Unavailable “Monthly and yearly report.”
Closing processing
When data collection is finished
Items to be generated at closing time
Select from “None,” “Minimum, maximum, average,” and “Minimum, maximum, average, total.”
*1:
*2: *3: *4:
FCN/FCJ control application variables with an OPC check. The data types of variables that can be collected are CData_REAL, CData_INT, REAL, LREAL, INT, SINT, UNIT, USINT, DINT, UDINT, BOOL, and STRING. Simple report can be transmitted by e-mail. (E-mail function is not supported by FCN-RTU (NFCP050) style S1.) Trigger is a Boolean type variable of control application. The interval between the closing triggers of logging block must be one minute or longer.
The data types that can be connected to the POU for logging data are CData_REAL, REAL, CData_INT, INT, and BOOL. FCN/FCJ control application variables with an OPC check. The data types of variables that can be collected are CData_REAL, CData_INT, REAL, LREAL, INT, SINT, UNIT, USINT, DINT, UDINT, BOOL, and STRING.
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
GS 34P02P53-01E
Feb. 2, 2011-00
10
<> <>
Table SOE Logging Function Specifications Item Periodic collection Data to be collected Number of sample Number of pretrigger sample Closing processing Items to be generated at closing time Simple report *1: *2: *3:
SOE Logging (*3) 100 milli seconds or longer (*1) POU for SOE logging (*2) 600 0 to 599 When data collection is finished
Filter Closing processing period Closing time File format Logging file size
Logging function
Data
Data collection Collect data POU for logging data
Data
Message logging 1 minute FCN/FCJ message 2 blocks (*1) ID of messages to be collected can be specified on a block basis 1 day 0 A.M. CSV format (*2) 1 file: Less than 1 MB (by default) Total: 1 to 500 MB (*3)
Total number of blocks for the message logging function. When the file closing processing is performed, the logging file is compressed in ZIP format. This logging file is compressed to 10% to 50% compared to the size of the original file. Specify the maximum size on a collection block basis. When the collected data is larger than the specified size, the oldest file is deleted.
TIME STAMP
Time stamp in data logging file, SOE file logging and message logging file is recorded based on FCN/FCJ clock and time zone of FCN/FCJ setting. Daylight saving time is not applied.
Data
40 items 40 40 items
F17E.ai
Figure POU for Logging
POUs for High-speed Logging There are high-speed synchronous POU and highspeed data collection POU (data types: REAL, INT, BOOL, CData_REAL, CData_INT).
POUs for SOE Logging There are SOE trigger POU and SOE data collection POU (data types: REAL, INT, BOOL).
LOGGING VIEWER Table Logging Viewer Function Specifications Item Tool View method Number of data items to be viewed *1:
Specifications Online: Specify URL with the Web browser Offline: Start the tool on a generalpurpose PC Trend, table format (*1) Table format view: up to 40 items Trend view: up to 10 items
Message logging file can be viewed only in table format.
LOGGING FILE COLLECTION FUNCTION SPECIFICATIONS Table Logging File Collection Function Specifications Item Applicable device File transfer mode Periodic collection Applicable file Amount of data to be saved *1: *2:
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
Block
Block Block
Logging file
Periodic collection depends on the scan period of the task. The data types that can be connected to the POU for SOE logging are REAL, INT, and BOOL. Not supported by FCN-RTU (NFCP050) style S1.
Item Periodic collection Data to be collected Number of blocks
*3:
FCN/FCJ
Control application
Unavailable
Table Message Logging
*2:
A POU for logging data is used to collect data at high speed.
Unavailable
MESSAGE LOGGING
*1:
POUs FOR LOGGING
Save
SOE LOGGING FUNCTION SPECIFICATIONS
Specifications FCN/FCJ: up to 32 units HTTP, FTP passive or FTP active Every 1, 2 , 3, 4, 6, 8, 12, and 24 hours (*1) All logging files Depends on the disk space of the PC (*2)
Logging files can also be collected manually whenever necessary. As for logging file collected in PC, you can select “automatic decompress” or “not automatic decompress.” Prepare a hard disk in which all data files can be saved, or remove unnecessary logging files on a timely basis.
GS 34P02P53-01E
Feb. 2, 2011-00
11
<> <>
LOGGING FILE TRANSMISSION (EMAIL) FUNCTION SPECIFICATIONS Table Logging File Transmission (E-mail) Function Specifications Item
Specifications SMTP (Specify the server type from the following options) E-mail transmission • SMTP (Standard) protocol (*1) • AUTH (User login is required) • PBS (POP before SMTP) E-mail address 5 addresses per group can be specified E-mail group 32 groups can be registered E-mail transmission Specify it in the e-mail group destination Transmit a logging file (*2) as an attached Logging file file (*3) Note: • Use E-mail Application Portfolio (InfoWell) to transmit FCN/FCJ messages and alerts by email. The logging file transmission (e-mail) function and E-mail Application Portfolio (InfoWell) can be used simultaneously. • Logging file transmission (e-mail) function is not supported by FCN-RTU (NFCP050) style S1. *1: For sending e-mails, an e-mail server is needed. Not only e-mail servers in the intranet but also external e-mail servers, such as internet providers can be used. When external e-mail servers are used, the firewall needs to be configured that e-mails can be sent to external e-mail servers. *2: The logging files that can be transmitted are described in the table below ”Logging Files for E-mail Transmission”. *3: A file compressed in Zip format is attached. File attachement is done by uuencode, so e-mail client needs to support uuencode function.
Table Logging Files for E-mail Transmission E-mail Item File Transmission Hourly logging file Hourly logging X Simple report Daily logging file Daily logging Simple report X Batch logging Batch logging file Snapshot logging file Snapshot Continuous X Simple report logging Triggered Snapshot logging file SOE logging SOE logging file Message logging Message logging file -
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
OPERATING ENVIRONMENT Autonomous Controller FCN/FCJ (Except FCN-RTU) Table Hardware Hardware Model (CPU) Style (CPU) System card
Description NFCP100 (FCN) or NFJT100 (FCJ) (*1) S2 or later More than 128 MB
Note: When there is possibility of power interruption in the electric supply to FCN/FCJ, please connect an uninterruptible power supply system (UPS). *1: Only single CPU can be used.
Table Software Software Operating software Revision
Remarks FCN/FCJ basic software (with Java function) R3.10.01 or later
Low Power Autonomous Controller FCNRTU Table Hardware Hardware
Description
Model (CPU)
NFCP050
Style (CPU)
S1 or later
Table Software Software
Description
Basic Software
FCN/FCJ Basic Software
Revision
R3.10.01 or later
License
For FCN-RTU, licenses are bundled with CPU module (Model: NFCP050). Select CPU modules with the portfolio licenses required.
GS 34P02P53-01E Aug. 9, 2012-00
12
<> <>
PC
The tables below show the operating environment for the following tools. • Logging Viewer • Logging File Collector • Logging Configurator Table Hardware Hardware Remarks Model IBM PC/AT compatible machine 1 GHz or higher 32-bit (x86) or Windows 7 64-bit (x64) processor CPU Pentium III 700 MHz or higher, or Windows XP Celeron 1 GHz or higher Windows 7 2 GB or larger recommended Memory Windows XP 1 GB or larger recommended Windows 7 Free space 20 GB or larger Hard disk Windows XP Free space 5 GB or larger Network Ethernet Media DVD-ROM
Table Software Software
Remarks Windows 7 Professional SP1 OS (*1) Windows XP Professional SP3 Windows Server 2008 SP2 (*6) Internet Explorer 8.0 + Windows 7 Java Plug-in 6.0 Update 21 (*2) (*3) Web browser Internet Explorer 6.0 SP3 + Windows XP Java Plug-in 6.0 Update 21 (*2) (*3) .NET Framework 3.5 (*4) Windows 7 (*5) .NET Framework 2.0 SP2 .NET Framework Windows XP (*4) Windows .NET Framework 2.0 SP2 Server (*4) (*5) *1: *2: *3:
*4:
*5: *6:
Only 32-bit version It is bundled with Application Portfolio Software Media. When it operates on the same PC with a VDS HMI client, version of Java Runtime Environment including Java Plug-in for both of them have to be the same. This is required for a PC that uses the logging file collection function, but is not required for a PC for the configuration function and viewing logging files. .NET Framework 2.0 or later is pre-installed in Windows 7 and Windows Server 2008. Only logging file collection function is supported.
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation
PERFORMANCE
The table below describes a rough guide of the CPU load of control application and the collecting capacity of logging function.
Autonomous Controller FCN/FCJ (Except FCN-RTU) Table The collecting capacity of logging function for FCN, FCJ (Guide) CPU load of Control AP 40% 25% 25% 10% 25% 20%
Number of logging block High Low SOE speed speed 0 25 0 0 25 0 0 10 15 0 10 15 3 3 2 3 3 2
Simple report e-mail transmission X (*1) X (*1) X (*1)
Note: • The capacity described in the table above is a rough guide of the performance. In case other functions such as Java function or transmission function are running simultaneously on FCN/ FCJ, the CPU load should be considered to be higher. • Configure the system secured enough to avoid any overloaded operation. *1: When all Simple Reports are sent by E-mail.
Low Power Autonomous Controller FCNRTU Table The collecting capacity of logging function for FCN-RTU (Guide) CPU load of Control AP 40% 25% 25% 10% 25% 20%
Number of logging block Low High speed SOE speed (*2) 0 16 0 0 16 0 5 11 0 5 11 0 3 3 1 3 3 1
Simple report e-mail transmission X (*1) X (*1) X (*1)
Note: • The capacity described in the table above is a rough guide of the performance. In case other functions such as Java function or transmission function are running simultaneously on FCNRTU, the CPU load should be considered to be higher. • Configure the system secured enough to avoid any overloaded operation. *1: When all Simple Reports are sent by E-mail. *2: FCN-RTU (NFCP050) style S1 only supports Low Speed type. (5 blocks for 40 %, 10 blocks for 25 %, 16 blocks for 10 %)
GS 34P02P53-01E May 31, 2012-00
13
<> <>
SOFTWARE DISTRIBUTION Software Distribution Media Logging Portfolio in the information transmission package (InfoWell) is provided in the FCN/FCJ Application Portfolio media (model number: NT205A).
Logging Portfolio License Note: Use of the following tools running on a PC does not require dedicated licenses. • FCN/FCJ Setup Tool for Logging Portfolio (InfoWell) • Offline Logging Configurator and Logging Viewer Applet • Logging File Collector
Autonomous Controller FCN/FCJ (Except FCNRTU) Logging Portfolio License includes an order sheet with an order ID and password on it. After purchasing the product, access Yokogawa’s Web site and enter your order ID and password to obtain your license ID. Register the issued license ID in the FCN/FCJ system card to enable you to use Logging Portfolio.
ORDERING INFORMATION Specify the model and suffix codes.
TRADEMARKS
• STARDOM is a trademark of Yokogawa Electric Corporation. • InfoWell is a registered trademark of Yokogawa Electric Corporation. • Microsoft and Windows are registered trademark of Microsoft Corporation in the United States and/or other countries. • Ethernet is a registered trademark of Xerox Corporation, the United States.v • Java is registered trademark of Oracle and/or its affiliates. • Other company and product names appearing in this document are trademarks or registered trademarks of their respective holders.
Low Power Autonomous Controller FCN-RTU For FCN-RTU, licenses are bundled with CPU module (Model: NFCP050). Select CPU modules with the Logging Portfolio License required.
MODEL AND SUFFIX CODES (EXCEPT FCN-RTU) Logging Portfolio License Table Software Model number
Suffix code
*1:
NT8016J NT8017J -L W 1 1
Remarks Logging Portfolio license (InfoWell) InfoWell License Pack (*1) License Order ID sheet delivery Always 1 Always 1 A Standard
This license pack includes the following four licenses. - NT8012J: Web Application Portfolio license - NT8013J: E-mail Application Portfolio license - NT8014J: Graphics Portfolio license - NT8016J: Logging Portfolio license
All Rights Reserved. Copyright © 2008, Yokogawa Electric Corporation Subject to change without notice.
GS 34P02P53-01E
Feb. 2, 2011-00
