MFCS/win 3.0

Transcription

MFCS/win 3.0

MFCS/win 3.0
Release
Notes
Version 3.0
File:
ReleaseNotes_3.0_SP3B.doc
Version: 3.0
Date:
May 2012
Printed in Germany
Sartorius Stedim System GmbH
Schwarzenberger Weg 73-79
D-34212 Melsungen
Tel. +49 (5661) 71-3400
Fax +49 (5661) 71-3702
http://www.sartorius-stedim.com
e-mail: [email protected]
CONTENTS
ABOUT RELEASE NOTES ............................................................................................................................................... 3 MFCS/WIN INSTALLATION ........................................................................................................................................... 4 UPGRADING FROM 2.1 TO 3.0 ............................................................................................................................................................ 4 Recipes created before 3.0 ................................................................................................................................................... 4 Control Unit Type for DFC Fermenter (Aplus, Bplus, Cplus) must be modified. .................................................. 5 OFF-LINE VARIABLE REPORT FOR OLD BATCHES FROM VERSION 2.0 ................................................................ 5 RECIPE INFORMATION ................................................................................................................................................. 6 PROFILE PHASE BECOMES ACTIVE, WHILE BEING MODIFIED................................................................................................................. 6 RENAME TRANSFER_BATCH_INFORMATION PHASE ........................................................................................................................... 7 WINDOWS SECURITY SETTINGS ................................................................................................................................. 8 READ ACCESS FOR ROOT DIRECTORY .................................................................................................................................................. 8 STARTING AND STOPPING MFCSKERNEL IN WINDOWS 7/VISTA/SERVER 2008 .............................................................................. 8 PROTECTION OF PROCESS DATABASES IN WINDOWS 7/VISTA/SERVER 2008 ................................................................................... 8 CHANGES FOR SP 2 .................................................................................................................................................... 16 REVISED MESSAGE TEXTS .................................................................................................................................................................. 16 ADDING PDF WRITING FUNCTIONALITY ............................................................................................................................................. 16 CYCLIC REFRESH IN PLO MODULE .................................................................................................................................................... 17 SETTING THE AFTER DECIMALS OF THE X-AXIS IN PLO MODULE ....................................................................................................... 18 NEW SYSTEM UTILITIES ...................................................................................................................................................................... 19 PID MODULE INSTALLATION .............................................................................................................................................................. 21 NEW SERIAL DRIVER TYPES CAN BE ADDED ...................................................................................................................................... 21 OPC ALARM AND EVENT CLIENT, MFCSOAEC........................................................................................................ 22 CONFIGURATION................................................................................................................................................................................. 23 Configuration of Physical Devices ................................................................................................................................... 23 Control Unit Parameters ..................................................................................................................................................... 23 Subscribe to Server ............................................................................................................................................................... 25 Message Filters ....................................................................................................................................................................... 26 Configuration of Variables ................................................................................................................................................. 27 Cyclic Variables ...................................................................................................................................................................... 27 OPC Variables.......................................................................................................................................................................... 28 Digital OPC Variable ............................................................................................................................................................. 30 CHANGES FOR SP 3 .................................................................................................................................................... 31 PHASENAME LENGTH AND COPYING COMPLETE OPERATIONS .......................................................................................................... 31 RESET OF STARTING/FINISHING BATCHES........................................................................................................................................... 32 CONTINUE BATCH FINISH AFTER TIMEOUT IF STORAGE MODULE OR RECIPE MODULE DOES NOT RESPOND IN TIME ....................... 32 MAINTENANCE FUNCTION FOR REPLICATED BATCHES ........................................................................................................................ 33 AUDIT TRAIL REPORT FOR ACTIONS WITHOUT VALUES CHANGE ......................................................................................................... 34 SETTING THE INITIAL VALUE FOR CALCULATED VARIABLES .................................................................................................................. 34 Variables without Control Unit......................................................................................................................................... 34 ENHANCED BATCH PROPERTIES.......................................................................................................................................................... 35 LOCKING OF UNCONNECTED CONTROLLER STATUS AS OPTION ........................................................................................................... 37 HANDLING OF OPC-QUALITY UNCERTAIN......................................................................................................................................... 38 All values are bad but the message “Error in Module OPCC : communication break” is not displayed at
the OPR Control Unit display. ........................................................................................................................................... 38 CONFIGURATION MANAGEMENT INCOMPATIBILITY WITH HP MANAGEMENT SOFTWARE ................................................................ 39 OPC CORE COMPONENTS INSTALLATION ON WINDOWS 7/SERVER 2008 ...................................................................................... 40 MFCS/win 3.0 Release Notes
2
About Release Notes
The MFCS/win Release Notes contain information that either is missing in previous versions of the
MFCS/win manuals or news about MFCS/win Service Packs. Service packs include improved
versions of the MFCS/win software modules for the actual MFCS/win release. They usually are free
of charge if downloaded from the Sartorius homepage from the Internet (http://www.sartoriusstedim.com).
MFCS/win 3.0 Release Notes
3
MFCS/win Installation
Upgrading from 2.1 to 3.0
Recipes created before 3.0
MFCS/win 3.0 supports viewing of 2.1 control recipes via Batch Report. However, execution of 2.1
recipes is no longer possible in the upgraded system.
In order to prevent the initialization of defined batches containing 2.1 recipes, the installation
program upon upgrade sets the status of these batches to “Deleted”.
Additionally, the process databases of the defined batches containing 2.1 recipes will be moved
from the batch folder (..\DATABASE\BATCHES) to a predefined folder
(..\DATABASE\BACKUP21\DEFINED_BATCHES).
4
Control Unit Type for DFC Fermenter (Aplus, Bplus, Cplus) must be modified.
If an MFCS/win system will be updated from 2.1 to 3.0 and a BIOSTAT® Aplus, Bplus or Cplus
is connected, the Control Unit Type must be changed from “DCU [Ethernet]” to “BIOSTAT A
/B /C plus [Ethernet]”.
Off-line Variable Report for old Batches from
Version 2.0
If a Batch Report for Off-line Variables for old Batches from version 2.0 shall be done with Batch
Report 3.0, then this cannot be done with the sub-report “Averaged Data” but it can be done
with the sub-report “Off-line Data”.
5
Recipe Information
Profile Phase becomes active, while being modified
A recipe with a profile phase is running and the profile phase has not been started.
Now the profile phase will be modified and the phase colour turns to yellow. The phase age
counter of the profile “Prf_STIRR” will start immediately after the transition “pO2 > 50” becomes
true or the previous phase has been finished. Even if the profile phase is still in mode modify. If
the modification will be finished 2.5 minutes later after the previous phase is finished, then the
profile will start at time 2.5 min.
Profile phase becomes active, while being modified
Profile continues at phase age 2.5 minutes, because the
previous phase was finished 2.5 minutes ago.
The profile phase age will start counting immediately when the previous phase is finished,
regardless whether the phase is being modified or not.
6
Rename Transfer_Batch_Information Phase
The Transfer_Batch_Information is used to synchronize recipes which are running on different
process units. Therefore the name of the corresponding Transfer_Batch_Information will be
referenced. Inside the Transfer_Batch_Information phase the phase name will be stored as a
string e.g. (“Wait_for_PU1”). If a phase name of a Transfer_Batch_Information phase will be
renamed, then the name must be also changed in the corresponding Transfer_Batch_Information
phase configuration in field “Phase Tag and Index”.
Rename of a Transfer_Batch_Information must be always done in at least two places
Example:
If the Transfer_Batch_Information phase “”Wait_for_PU1” will be renamed in reipce
“Recipe_Production”, then the name must be also changed in the Transfer_Batch_Information
phase “Wait_for_PU2” in field (Phase Tag and Index) in recipe “Recipe_Seed”.
7
Windows Security Settings
Read Access for Root Directory
It is necessary that the Windows users who shall work with MFCS/win have at least “Read Access”
to the root directory of the hard disk where MFCS/win is installed.
Consider the following setup:
Windows 2003 Server with MFCS/win installed on D:\mfcs_win\. The user "test" has only access
rights to D:\MFCS_win\, but no rights (neither read nor write) to D:\. When the user opens the
MFCS/win Sample Data Manager (SDM) for any batch, SDM opens the batch and displays the
error "An unnamed file contains an invalid path.". The user cannot work with the batch.
Starting and Stopping MFCSKernel in Windows 7/Vista/Server
2008
To start and stop the MFCS/win Kernel using the MFCS/win Service Control Program MFCSSCP, it
is necessary to start MFCSSCP with an Administrator’s token in Windows Vista. To do this, rightclick the MFCSSCP icon and choose “Run as Administrator”. Otherwise the attempt to start/stop
the kernel will fail with an “Error in open service” message box. This is due to the restriction that
without an Administrator’s token, Windows services such as MFCSKernel cannot be started or
stopped in Windows Vista/2008 due to the new User Account Control (UAC) component of
Windows.
Protection of Process Databases in Windows 7/Vista/Server
2008
It is the customer’s responsibility to disable deletion or moving of MFCS/win batch databases on
file level. By setting permissions on a file or folder, you specify the groups and users whose access
you want to restrict or allow, and then select the type of access. File and folder permissions can
be set only on NTFS drives. The default permissions are “Read Only” and allow everybody only to
read process databases on file level e.g. with the Windows Explorer.
The MFCS/win process databases will be stored to folder \MFCS_WIN\DATABASE\BATCHES by
default. We recommend restricting the permissions to avoid deletion of any process database.
Attention:
The runtime part of MFCS/win requires full control to all folders. Do not restrict
the permissions except of sub-folder \...\BATCHES and follow the description
given below carefully.
8
Open Windows Explorer and go to folder “BATCHES”. Right-click on
the folder and select “Properties”.
Right-click on
folder “BATCHES”
Click menu
item “Properties”
9
Go to tab “Security” to see the default permissions for groups and users.
Select “Advanced”.
Click tab
“Security”
Click button
“Advanced”
Select “Edit” to modify the groups and permissions.
Click button
“Edit”
 10
Deselect “Include inheritable permissions from this object’s parent” in
order to customize the permissions of specific folders.
Uncheck
“Include inheritable
permissions…”
The following dialog will immediately appear after deselection. Select
“Remove” to remove all existing permissions of the folder.
Click button
“Remove”
 11
Select “Add” to create a new permission entry.
Click button
“Add”
Type “Everyone” and select “OK”.
Enter group
“Everyone”
Click button
“OK”
 12
Select all permissions except “Delete subfolders and files” and “Delete”.
Select “OK”.
Check all permissions
except “Delete
subfolders and files”
and “Delete”
Click button
“OK”
Select “Add” to create another permission entry.
Click button
“Add”
 13
Type “SYSTEM” and select “OK”.
Enter group
“SYSTEM”
Click button
“OK”
Select all permissions and select “OK”.
Check all permissions
Click button
“OK”
 14
Select “Replace all existing inheritable permissions on all descendants
with inheritable permissions from this object” and select “OK”.
Check “Replace
all existing…”
Click button
“OK”
The following dialog will immediately appear. Select “Yes” to cascade the
permissions to the process databases.
Click button
“Yes”
Click “OK” on all open dialogs to save the new settings.
Please note:
This change is made on operating system level and will
influence the MFCS/win function “Batch Delete” and
“Batch Move” inside the Batch Management. After
performing one of these functions, you will get a message
that the function was not successful.
 15
Changes for SP 2
Revised Message Texts
Some Message Texts written to the MFCS.MEV File form e.g. the MFCSREPL Module have been
changed. If an existing Remote Alarming installation reads the MEV file and filters for these
strings, it must be adapted.
Adding PDF writing functionality
The PDF writing tool PDFCreator is added to the installation CD. You can find in the
folder: “SupportTools\PDF\PDF Creator”.
 16
Cyclic Refresh in PLO Module
Plots are closed and re-opened once a day or each 1000 update cycles. The customer can control
how often the plots shall be closed with the entry “MaxUpdate_n” in section [MFCSPLO] in the
WKST.ini. The WKST.ini is in the folder: “…\MFCS_win”.
Example in WKST.ini:
[MFCSPLO]
MaxUpdate_1=1000
The switch "MaxUpdate_" shall be treated as follows:
1.
MaxUpdate_n=1000
No change in behaviour to 3.0SP1. If cyclic refresh is active, then the plots will be closed
after 1000 update cycles or once a day during midnight.
2.
MaxUpdate_n > 1000 and < 9999
If cyclic refresh is active, then the plots will be closed after MaxUpdate_n update cycles.
They will never be closed during midnight.
3.
MaxUpdate_n=9999
The plots will never be closed. It is recommended, that the customer closes the plots after
the batch has been finished.
The customer has the responsibility to check the memory usage of the plotting module,
because there is the risk, that the computer runs out of memory and the MFCS/win
storage program stops storing.
 17
Setting the after decimals of the x-axis in PLO Module
The value for the after decimals of the x-axis can be set with the entry “AfterDecimalsTime” in
section [MFCSPLO] in the WKST.ini. The WKST.ini is in the folder “…\MFCS_win”.
Default Entry in WKST.ini:
[MFCSPLO]
AfterDecimalsTime=3
The numbers 0, 1, 2, 3, 4, and 5 are valid. If a different value is found, the default setting 3 will be
used.
Example with the value 10:
Entry:
AfterDecimalsTime=0
AfterDecimalsTime=1
AfterDecimalsTime=2
AfterDecimalsTime=3
AfterDecimalsTime=4
AfterDecimalsTime=5






Effect:
10
10.0
10.00
10.000
10.0000
10.00000
Default Value
 18
New System Utilities
The following System utilities were added.
FileVersion:
This utility shows the release version and the installed version. The result shows a difference or an
agreement between each other.
Example:
 19
Maintenance Tool:
This is a MFCS/win service utility to reproduce a customer bug for example. If the customer has a
problem and the MFCS/win services need more details about the config e.g. this tool produces a
zip file with some details about the configurations and databases.
Repair MFCSBRP:
If the batch report is damaged, this tool repairs the MFCSBRP Database.
Repair MFCSCMA:
If the Configuration Manager is damaged, this tool repairs the MFCSCMA Database
Show Dongle Contents:
This utility shows an info message about your MFCS/win license and your possibilities .
Example:
 20
PID Module Installation
To install the PID Module open the folder (..\MFCS_win\Driver Setups\MFCSPID).
Double click the “Activate_MFCSPID.reg” registry entry and choose “yes” on the following
message box.
Then you have to restart the MFCS Server and the PID Module is installed.
New Serial Driver Types can be added
The additional Serial Driver Types MFCSRSD and MFCSADI1060 can be added to the MFCS/win
installation.
MFCSRSD:
The MFCSRSD is a MFCS/win Serial Driver for communicating with the Respironics Capnostat 5.
This device is a CO2 Analyser.
MFCSADI1060:
The MFCSADI1060 is a MFCS/win Serial Driver for communicating with the ADI-1060 Control
Units.
 21
OPC Alarm and Event Client, MFCSOAEC
The OPC Alarm and Event Client (OAEC) processes alarms and messages generated by different
OPC A&E servers. All control units send their values (measured, calculated or manually entered) to
the Memory Resident Datapool (MRD), which checks their validity against the instrument ranges
and alarm limits (low, low low, high, high high and the deviation alarm limits) before storing
them to the Datapool. If alarming is enabled for the variable, MRD will change the status of the
variable to an alarm state, construct an alarm and send it to OAEC. In addition, when the alarm is
acknowledged by the operator or the value returns to a normal state, another alarm will be
generated by the MRD and sent to the OAEC. For acknowledgment and returning alarm messages,
OAEC will find the corresponding coming alarm and store all of them into the same alarm log
record.
The alarm message will be available in MFCS. There and in the OPC Server the alarm can be
acknowledged.
Furthermore, control units can generate their own alarms and messages and send them to MRD.
For all modifications that may influence the process, like setpoint changes or other operator
actions, MRD will create messages with time and user/subsystem name. All these messages will be
sent to OAEC.
When an alarm or message arrives in the OAEC, it will check the type and perform the required
actions. For all alarms and messages, the default actions are displayed in the OAEC window and
stored in the batch database. Alarms will be stored in the AlarmLog table and the messages in the
MessageLog table. The OAEC window will buffer the last 1000 “alarm message” lines, and the
whole buffer or part of it can be printed out. For alarms, other actions are specified in alarm
blocks, which can be selected individually for each variable and alarm type in the variable
configuration. Available actions are activation of the beeper or requesting the MFCS/win shell to
pop-up an alarm dialog.
The OAEC is providing this functionality since MFCS/win 3.0 SP1a, before the functionality was
provided by AML.
Alarms will be mapped to first matching target of the following list:
- Alarm High High
- Alarm High
- Alarm Low
- Alarm Low Low
- Userchange
- Alarm Submessage
- Alarm Userinfo
- Alarm Subalarm
- Batchevent
 22
Configuration
Configuration of Physical Devices
Control Unit Parameters
For Control Unit type OPC the following dialog appears:
OPC DA tab
Identification Group:
Parameter
Computer Name
Server Name
Parameters Group:
Parameter
Update Rate
The identification parameter describes the control unit and opc
interface
Description
The computer name where the
opc server is located
The name of the opc server for
the control unit
In the parameters group, communication specific parameters can be
defined which may differ between control units.
Description
Update Rate of OPC Items in
 23
seconds
The time (in seconds) that the
driver waits for a response from
the opc server until it reports a
communication error
Timeout
OPC A&E tab
Parameter
Computer
Name
Server Name
Update Time
Buffer Size
Retry Time
Locale ID
Description
Computer Name of the OPC A&E Server
Type
String
OPC A&E Server Name
Time between event notifications
Maximum number of Events
Retry time in seconds after connection loss
ID for language of events.
1033 = English – United States
1031 = German – Germany
1036 = French – France
3082 = Spanish - Spain (Modern Sort)
for more locale ids see:
http://www.microsoft.com/globaldev/reference/lcidall.mspx
String
Integer
Integer
Integer
Integer
 24
Subscribe to Server
In this window it is possible to select the OPC A&E Server.
By default all alarms will be delivered. With the Types, Categories, Areas and Sources tabs it is
possible to create a preselection of the alarms & events that will be sent to the client. Use this
preselection to reduce the network and server load.
Types Tab
After checking Enable type filtering messages will be filtered by
Type. It is possible to add or remove message types, that should be
received. Default enabled are Condition Event, Tracking Event and
Simple Event.
Categories Tab
Message filtering by categories.
Areas Tab
Message filtering by area
Sources Tab
Message filtering by source
 25
Message Filters
In the message filter dialog it is possible to map alarms and events received from the OPC A&E
server to the corresponding MFCS/win alarm or event categories.
Available categories are User Messages, User Actions and Control Unit Messages.
To map the OPC message, create a filter using the following OPC tags.
Source
Source Tag of the OPC A&E packet.
Message
Message string of OPC A&E packet.
Severity
Severity range of the message.
Condition
Condition of the message.
Subcondition
Subcondition of the message.
If an OPC message matches the filter for this category, the OPC message will be converted to an
MFCS message of this category.
 26
Configuration of Variables
Cyclic Variables
Limits
Alarm Mode
Inactive:
MFCS:
MFCS / Instr:
Control Unit:
OPC AE:
Alarming will be disabled by the system for this variable
MFCS/win will check the value against the alarm condition
and will create and administrate the alarms.
MFCS/win will check the value against the alarm condition
and will create and administrate the alarms. Additional an
instrument alarm is given, if the measured value is outside
the defined range.
The control unit (DCU) will send the alarm status of this
variable to MFCS/win, which interprets and rebuilds the
whole control unit alarming. A return to normal cannot be
protocolled.
The OPC A&E Server will send the Alarm status and alarm
message of this variable to MFCS/win, which interprets and
rebuilds the whole control unit alarming.
 27
OPC Variables
This is the driver configuration dialog for Cyclic Variables, DCU, FIS, and FIS PID Controller of a
OPC control unit. Depending on Variable Type and Alarm mode the Controller Tags Group and
Alarm Tags Group are enabled.
The Controller Tags group is enabled if variable type is one of DCU, FIS or FIS PID controller.
The Alarm Tags group is enabled if the alarm mode of the variable is set to OPC AE.
Process Value Tag Group
Value
Name of the OPC Tag at the OPC DA Server for the Value.
Controller Tags Group
Setpoint
OPC Tag name for variable setpoint.
Ouput
OPC Tag name for variable output.
 28
Mode
OPC Tag name for variable mode.
Status
OPC Tag name for variable status.
Alarm Tags Group
Alarm Limit LL
Filter for variable low low value.
Alarm Limit L
Filter for variable low value.
Alarm Limit H
Filter for variable high value.
Alarm Limit HH
Filter for variable high high value.
OPC AE Server Filter Group
In this group message filters for alarms can be defined.
If an alarm or event received from an OPC A&E server matches the filter, it will be mapped to the
corresponding MFCS alarm (high high, high, low, low low) that was selected.
Source
Source tag.
Message
Message tag.
Severity
Severity range.
Condition
Condition tag.
Subcondition
Subcondition tag.
These fields are AND connected, so every field has to match in order to filter the alarm.
 29
Digital OPC Variable
This is the driver configuration dialog for a digital OPC variable.
The button Filter enables to define a filter which A&E messages will be mapped to an alarm.
Process Value Tag Group
Value
Name of the OPC Tag at the OPC DA Server for the Value.
Alarm Tags Group
-
Alarm Mode: Name of the alarm OPC Tag
 30
Changes for SP 3
Phasename Length and Copying complete Operations
The maximal possible character length for a phase name is changed from 32 characters to 25
characters. The other 7 characters were needed to set the string “CopyXX_” in front of the phase
by copying the complete operation. After copying a complete operation the copied phases are
named “Copy_XX + Source Phase Name” instead of “Copy_XX_of_ + Source Phase Name”. The
reason therefore is that there was a bug: by copying an operation with phase names which were
32 characters long, the editor crashes by string overflow.
Example:
An old copied Operation:
A new copied Operation:
 31
Reset of starting/finishing Batches
If the Initialization and/or Batch Finish cannot be completed for any reason, (the batch status remains ‘starting’ or
‘finishing’) the function Reset starting/finishing Batches will set the status of the batch back.
The following table shows the possible status changes and the connected action:
old status
database
starting
starting
starting
finishing
finishing
online
starting
running
running
Batch execution finished
???
finishing
new status
database
defined
defined
running
running
finished*
action
online
Remove batch from online
system
running
running
Batch execution finished
Remove batch from online
system
finished*
Continue Batch Finish after timeout if Storage Module or
Recipe Module does not respond in time
During Batch finish MFCS/win informs the storage module and the recipe module to finish their
activities for the batch in question. If this is not done in time, the finish process continues after a
timeout.
 32
Maintenance function for replicated batches
The Maintenance functions may be required for repairing batches or batch status information after abnormal
behaviours, which may occur after computer system crash (power failure, unstable network connection…).
If the Replication Module is installed a maintenance function for replicated batches is available.
The Replication Module creates backup copies for running Batches on a file server. During batch finish this copies are
turned to the masters.
To free the allocated space on the MFCS/win Server you can use the maintenance function Replicated Batches.
You will get a list of replicated batches together with information about Modify date and size on the MFCS/win
Server and on the file server. Normally the file server should contain the newest copy of the batch database. If this is
not the case, the line is marked read.
Select one or more batch from the shown list and activate the menu item Delete from MFCS/win Server in the
context menu.
To see a list of finished batches which are not correctly replicated select the Show option Not replicated yet.
To copy batch databases to the file server and to use them as master select one or more batch from the shown list
and activate the menu item Perform Replication Action in the context menu.
For both option you can use the Filter function to limit the shown list. In addition it is possible via the file menu to
print the list or to export it as csv file.
 33
Audit Trail Report for actions without values change
- Audit Trail
Configuration changes relevant for the selected batch. Filters for
the Audit Trail can be set.
Filters for the Audit Trail
Do not enter * for New Value or Old Value if you want to see actions in which the value is not
changed!
Setting the initial value for calculated variables
Variables without Control Unit
It is possible to define variables where the configuration field for control unit for the following variable
types is empty.
Cyclic Variables, Controllers, Digital Variables
The control unit specifies which control unit (subsystem) is allowed to set or write the value of the
variable. If the control unit is set to Calculation Manager, then only the Calculation Manager and the
Recipe Execution Manager are allowed to write the value. Via a Recipe the value can only be set as long
as no calculation is active. If the control unit is set to a connected control unit, the MFCS module that is
doing the communication with this control unit is allowed to write the values.
If the control unit field is empty, then each module is allowed to write the data. There are two cases were
it is necessary to keep the control unit field empty.
Details of On-line Calculations
With the “Details” button, the Calculation Detail form can be opened. These settings will describe the start
values and behaviour of the on-line calculation. For most on-line calculations, it is not necessary to open
this window.
The exceptions are formulas with recursive structures that require an “initial value” and if one algorithm is
divided into several formulae, then the order in which the calculations shall be performed (Calculation
Order) is important.
 34
Window for details of On-line Calculations
Initial value
Calculation
Order
Initial value (start values) must be set for recursive structures (e.g. A = A + 1 like
counters). The result of the calculation will be set to this initial value when the calculation
is started via a recipe.
Up to MFCS/win 3.0 SP3 the initial value was only applied if no valid value was available.
Since MFCS/win 3.0 SP3, if an initial value is configured, the old value will always
be overwritten during calculation start.
Defines the order when a calculation will be performed. All calculations will be done for
each _MFCSCalcCycle (default value 15 sec). The calculations will be performed in the
order of the defined order number. The calculation with the lowest order number will be
done first starting with zero. The calculation order is a value in the range from 0 to 255.
Skip Calculation
if Input INVAL
This setting can be used to control the behaviour of an on-line calculation, if one input
parameter is INVALID. If this option is active, then the calculation will be skipped, until all
input parameters are valid again. The actual value will remain unchanged until the next
valid calculation.
Enhanced Batch properties
The following process unit, control unit and variable properties can be configured for access via OPC. All
properties printed in bold are available in the standard configuration, others can be added.
Property
Write
Values
ProcessUnit_description
no
String
NextBatchName
yes
String
BatchName
no
String
Batch_ID
no
byte values
Batch_description
no
String
Batch_status
no
String
Batch_database
no
String
creation_date
no
Date time
finish_date
no
Date time
 35
syncronisation_date
no
Date time
Backup_cycle
no
long
Scan_cycle
no
long
Operator
no
String
Supervisor
no
String
Recipe
no
String
Operation_tag
no
String
Phase_tag
no
String
Info 1
no
String
Info 2
no
String
Info 3
no
String
Info 4
no
String
Info 5
no
String
Info 6
no
String
Info 7
no
String
Info 8
no
String
Info 9
no
String
Info 10
no
String
Property Descriptions:
ProcessUnit_description
NextBatchName
BatchName
Batch_ID
Batch_description
Batch_status
Batch_database
creation_date
finish_date
syncronisation_date
Backup_cycle
Scan_cycle
Operator
Supervisor
Recipe
Operation_tag
Phase_tag
Info 1 - Info 10
Entered Process Unit description
Predefined the next Batch name
Entered Batch Name
Index where the batch is running
Entered Batch description in Batch Details
Shows the state of the batch in a binary value
Location and Filename of Batch
Date and time when Batch was created
Date and time when Batch was finished
Date and time of synchronisation in Operator Service
Configured backup interval in minutes
Configured scanning interval in seconds
Entered Operator in Batch Details
Entered Supervisor in Batch Details
Running recipe name, if batch has a recipe
Actual running operation, if a recipe is running
Actual running phase in recipe, if a recipe is running
Additional batch information’s which are entered in Batch Details
 36
Locking of unconnected controller status as option
Via the LockUnconnectedCtrStatus entry for each Control Unit n it is possible to disable the change of the Controller
Status if the Controller Status is not linked to an OPC-Tag.
LockUnconnectedCtrStatus_n=0
LockUnconnectedCtrStatus_n=1
Allow change of controller status
Do not allow change of controller status
If no entry is configured for a Control Unit it is allowed to change of controller status.
 37
Handling of OPC-Quality uncertain
All values are bad but the message “Error in Module OPCC : communication
break” is not displayed at the OPR Control Unit display.
Solution:

For OPC-Tags with the quality uncertain the value bad is shown, but for the break
decision this tags are counted as valid. Use an OPC-Client which shows the Quality of the
OPC-Tags and check the all configured items.
 38
Configuration Management incompatibility with HP
Management Software
It may be possible that the Configuration Management Program will not start on Computers that have the Software
“HP Protect Tools Security Manager” installed. Instead, it displays an Error similar to the one in the following
screenshot:
Either uninstall the software “HP Protect Tools Security Manager”, or stop the software when starting the
Configuration Manager: Start a DOS-Commandline with Administrative Privileges and type “taskkill /f /im DP*”. Then
start the Configuration Manager.
 39
OPC Core Components installation on Windows 7/Server
2008
Sometimes the installation of the OPC Core Components fails under Windows 7 or Windows Server 2008. To
manually install the OPC Core Components, click start, type cmd and right-click the cmd.exe in the results list. Click
“Run as Administrator” to run the command shell with administrative privileges. Change the directory to the
directory where the MFCS OPC Server installation is located by typing e.g. “cd /d d:\OPCServer”, then change
directory into the subdirectory SupportTools Folder where the OPC Core Components installation is located.
Type “msiexec.exe -i OPC Core Components 2.00 Redistributable 2.30.msi” (including the quotation marks) to start
the installation. This starts the manual installation.
 40

MFCS/win 3.0

Transcription

Similar documents

ST STEPEHNS GREEN MAP

High School Seniors: Make an “A”– Maybe win this

Silky Smooth Elegancy

Everything you need for the holidays!

2016 Events Brochure - WIN of Philadelphia

Learning from Chakde Movie

Thunder Run 2014

june 4 : fado irish pub

PDF Version - 1.32 MB

Milwaukee Golf Show Poster2013