Professional Documents
Culture Documents
Warning
! means that death, severe injury or serious material damage can result if the
corresponding safety precautions are not followed carefully.
Caution
! means that material damage or minor injuries can result if the corresponding
safety precautions are not followed carefully.
Caution
means that material damage can result if the corresponding safety precautions
are not followed carefully.
Attention
refers to important information on the product, handling of a product or a
corresponding segment of the documentation to which special attention should be
given.
Qualified Personnel
Commissioning and operation of a device may only be performed by qualified personnel. Qualified personnel in a
technical safety sense within this product info are personnel that have the authorization for commissioning, grounding
and identifying all devices, systems and circuits according to the applicable technical safety standards.
Intended Utilization
Warning
! The device may only be utilized with the replacement parts described in the catalog and the technical
description and only with foreign or external devices and components that are approved or suggested
by Siemens.
Fault-free and safe operation of the product depend on proper transport, proper storage, assembly,
installation, operation and maintenance.
iv SIWAREX FTA
SIWAREX FTA
Contents
SIWAREX MULTISCALE
Preface 1
Scope of Delivery 2
Software package for batching
plants
Product Overview 3
Information for the Operator 4
Product Info
Configuring 5
Technical Data 6
7
Issued 03/2004
Order number 7MH4900-2AL01
SIWAREX FTA v
Contents
1 Preface.................................................................................................................................... 1-1
1.1 PURPOSE OF THE PRODUCT INFORMATION ................................................................................ 1-1
1.2 BASIC KNOWLEDGE REQUIRED ................................................................................................. 1-1
1.3 FURTHER SUPPORT .................................................................................................................... 1-1
2 Scope of Delivery .................................................................................................................. 2-2
2.1 SCOPE OF DELIVERY AND SYSTEM REQUIREMENTS .................................................................. 2-2
3 Product Overview .................................................................................................................. 3-3
3.1 GENERAL .................................................................................................................................. 3-3
3.2 BENEFITS................................................................................................................................... 3-4
3.3 APPLICATION RANGE ................................................................................................................ 3-4
3.4 STRUCTURE ............................................................................................................................... 3-5
3.5 FUNCTION ................................................................................................................................. 3-5
3.6 COMMISSIONING- AND SERVICE WITH SIWATOOL FTA......................................................... 3-8
4 Information for the Operator ................................................................................................ 4-9
4.1 GENERAL .................................................................................................................................. 4-9
4.2 START SCREEN .......................................................................................................................... 4-9
4.3 SECTION SELECTION MENU ......................................................................................................4-10
4.4 OPERATOR SECTION .................................................................................................................4-10
4.4.1 Input Recipes ...................................................................................................................4-10
4.4.2 Store Recipes in SIMATIC HMI ......................................................................................4-12
4.4.3 Dosing Status...................................................................................................................4-12
4.5 SERVICE SECTION.....................................................................................................................4-13
5 Configuring .......................................................................................................................... 5-17
5.1 COMMAND GROUPS..................................................................................................................5-17
5.2 AUTOMATED STATUS TRANSITIONS .........................................................................................5-18
5.3 CONFIGURING STEPS ................................................................................................................5-21
5.3.1 Configuring the Devices ..................................................................................................5-21
5.3.2 Response to Errors ..........................................................................................................5-23
5.3.3 Configuring the Material Records...................................................................................5-24
5.3.4 Configuring an Additional Scale .....................................................................................5-24
5.3.5 Configuring the Data Structures .....................................................................................5-25
5.3.6 Symbol list .......................................................................................................................5-33
5.3.7 Tables of display texts for the FC blocks.........................................................................5-34
5.4 MESSAGES................................................................................................................................5-35
5.5 CONFIGURING WITH PROTOOL .................................................................................................5-36
6 Technical Data ..................................................................................................................... 6-37
6.1 PROGRAM SCOPE ......................................................................................................................6-37
6.2 CYCLE TIME .............................................................................................................................6-37
7 Accessories ......................................................................................................................... 7-38
Illustrations
FIG. 3-1 TYPICAL CONFIGURATION FOR SIWAREX MULTISCALE...................................... 3-4
FIG. 3-2 PROGRAM STRUCTURE I STEP7 FOR SIWAREX MULTISCALE.............................. 3-6
FIG. 3-3 PROGRAM STRUCTURE II STEP7 FOR SIWAREX MULTISCALE ............................ 3-7
FIG. 3-4 INITIAL COMMISSIONING WITH SIWATOOL FTA .................................................... 3-8
FIG. 4-1 SIWAREX MULTISCALE START SCREEN .................................................................... 4-9
FIG. 4-2 SIWAREX MULTISCALE MENU SCREEN....................................................................4-10
FIG. 4-3 INPUT RECIPES ................................................................................................................4-11
FIG. 4-4 COMPONENT NAMES ....................................................................................................4-11
FIG. 4-5 STORE RECIPES IN TP.....................................................................................................4-12
FIG. 4-6 DOSING STATUS ..............................................................................................................4-13
FIG. 4-7 SELECT SERVICE SECTION ...........................................................................................4-14
FIG. 4-8 VIEW OF AN INDIVIDUAL SCALE................................................................................4-14
vi SIWAREX FTA
SIWAREX FTA
Tables
TABLE 5-1 DISPLAY TEXT FOR FC40 TASK MANAGER ......................................................5-34
TABLE 5-2 DISPLAY TEXT FOR SIWAREX FB31DEVICE .....................................................5-35
TABLE 5-3 DISPLAY TEXT FOR FC34 CHECK-AND-LOAD TASK LIST .............................5-35
TABLE 6-1 REQUIRED MEMORY ..............................................................................................6-37
TABLE 6-2 CYCLE TIME .............................................................................................................6-37
1 Preface
This product information will provide you with all the information you will need for
configuring the plant with SIWAREX MULTISCALE for several SIWAREX FTA
modules; it also contains information on operating the plant using the TP170B
touch panel.
Do you have any questions about using the SIWAREX FTA or SIWAREX
MULTISCALE? Then please contact your Siemens representative in the office or
business location that is responsible for your area or technical support for
SIWAREX Tel.: +49 (0)721 595 2811.
Updated information on SIWAREX Weighing Technology can be found on the
respective Internet Site.
http://www.siwarex.com
2 Scope of Delivery
3 Product Overview
3.1 General
The SIMATIC HMI TP270B shows the current status of the active recipe. The open
part of the software is extensively commented so that the user can change, extend
and easily adapt the software to customers' wishes.
3.2 Benefits
SIWAREX MULTISCALE is the ideal solution in any situation where there are
benefits to be gained from integrating weighing technology directly into the
automation system. The weighing is then a part of complex processes which are
controlled by the automation system. SIWAREX FTA and SIWAREX MULTISCALE
software enables batching plants to be developed cost-effectively.
Typical application ranges:
o Multi-component dosing for a scale
o Multi-component dosing of more than one scale according to a recipe
3.4 Structure
3.5 Function
The control of the weighing procedure is completely run from the weighing module
as if in separately constructed weighing electronics. The integration in SIMATIC
enables the progress of the weighing procedure to be influenced directly from the
PLC program however. In this way you get a useful job distribution: the very fast
weighing functions are implemented in the SIWAREX module, the locks and signal
links in the PLC.
SIWAREX MULTISCALE is responsible for recipe-controlled program tasks in the
SIMATIC S7. In SIWAREX MULTISCALE, calls of the relevant scales are
coordinated, commands and setting values are passed to the scales according to
progress of the process, and the data from the scales are prepared for
visualization.
.
4.1 General
This information for the operator aims to describe the operation and monitoring of
the weighing plant. The description corresponds to the as-delivered state of the
SIWAREX MULTISCALE software.
The description of the individual scale parameters and scale functions can be
found in the SIWAREX FTA manual and are not explained individually in the
display of the individual screens by SIWAREX MULTISCALE.
This product information presents only the facilities available in the individual
screens.
- Input recipes
- Store recipes
- Dosing status
Inputting recipes is very straightforward. The operator specifies the numbers of the
desired components and the associated setpoints. He can switch to the
"Component Names" screen to obtain an overview of the components.
This screen allows the component names to be viewed and/or edited. The
component names are stored in a data module in the SIMATIC_CPU.
This screen allows the recipes to be stored in TP/OP. This is a standard ProTool
screen, and its layout cannot be modified.
Fig. 4-5 Store recipes in TP
Dosing Status allows the process to be observed and monitored. Once the recipe
has been loaded from the Input Recipes screen it is ready to start.
The whole recipe can be started, paused, aborted, or resumed following a pause.
Irrespective of the commands affecting the entire recipe, each line of a recipe can
also be controlled "manually". This separate manual control of a recipe line is
useful in the event of problems. The component in question can be controlled
completely separately, independently from the overall progress of the recipe.
The "Status" columns can be used to establish the current status of a component.
The status is described with an abbreviation and a number. This allows you to
establish clearly the stage at which the component will be dosed.
The service section enables a number of service activities to be carried out. These
should not be performed by anyone other than a qualified service technician. The
range of service activities can be extended on a plant by plant basis.
Component properties
A set of parameters is maintained for each component. The parameter set contains
the material-specific properties of a component.
This screen shows the statuses of individual devices as defined in the status
diagram.
5 Configuring
The SIWAREX MULTISCALE software is configured to operate with one scale. The
addition of an extra scale is coded in the form, for instance, of commented-out
subroutines. To extend the software to cater for more than 2 scales, both the
program calls in the STEP7 program and the screens and variables must be
extended in ProTool in accordance with the specified strategy.
The standard function SIWAREX FTA -FB41, the standard module device
SIWAREX FTA – FB31, the task manager FC40 and certain help FCs are
protected and cannot be modified by the user. All other program modules, FCs,
DBs and UDTs are accessible and can be customized for the application in
question. The number of components in the recipe, the quantity of material data
and the number of scales are all freely definable. The only constraint in this respect
is SIMATIC system resources, which have to be taken into account.
Each class has input and output interfaces, and any communication with other
classes must take place through these interfaces. The signals (commands or
statuses) are forwarded from one class to the next.
The Task Manager calls all lines in sequence. If a line is active, then the assigned
device driver is called and the device is addressed.
The following three diagrams illustrate the automated status transitions for each of
the three SIWAREX MULTISCALE classes. The transitions between the statuses
in each class are evaluated by the other classes and, in turn, bring about new
status transitions.
The automated status transitions store an "Autostate" number reflecting the status
in the data structures of each class.
The connection between input and output signals is described in the status
diagram in the following figure, which uses the automatic status changes in the
"Device SIWAREX FTA" as an example.
If the status of the scale is not active, then the input signal start will have the effect
of changing the status to starting up.
The status will automatically change to finished if the setpoint in the corresponding
line is zero or an abort is requested.
If a setpoint is not zero, then dosing data I, setpoint and start command are
transferred to SIWAREX FTA. If an error occurs here, then the status reverts
automatically to active and waits for the Continue command before attempting the
transition to starting up again.
The status changes automatically to running once dosing has commenced.
Once SIWAREX FTA has sent the message "Weighing cycle complete", the status
is changed from running to finished via the status shutting down.
Not until the input signal ExtEndSignal is received does the status change
automatically to non active. (In the example, project signal ExtEndSignal always
has a logical value of 1; however, the user can change this during configuring - see
FC36 Enable Conditions).
If an error occurs during dosing (status running) or if the automatic status manager
receives the signal stop, then the stopped status is assigned.
With the signal continue the automatic status manager moves from stopped to
restarting and then on to running.
The automated status transitions for the Task Manager operate in a similar way but
are generally simpler, as certain statuses are not used.
The status running in the Task Manager automatic status manager is shown on a
separate diagram.
The status diagrams are printed to help you understand how SIWAREX
MULTISCALE works.
The configuring steps outlined here should become clearer when you study the
example project plan we have included.
In its as-delivered state, the plant is prepared for an installation with two scales.
When recipe-controlled, both scales are dosed simultaneously.
Scale 1 = Device 1
Scale 2 = Device 2
.
.
The SIWAREX MULTISCALE main program, which processes the current recipe
(task list), is also viewed as a device in logical terms and is assigned the number 5
in the DB34 DB_DEVICE_LIST.
If SIWAREX MULTISCALE is used for more than one production line, it is
advisable to create a separate DB_DEVICE_LIST for the logical devices of type
Task Manager.
When a scale needs to be addressed, it is called specifically by the function FC35
– FC_CALL_DEVICE. This function controls the scale via the driver FB31 –
DEVICE SIWAREX.
In order to check the dependences between the devices, function FC40 TASK
MANAGER calls function FC36 - ENABLE_CONDITIONS once per cycle.
To prevent all the devices included in the recipe from starting to work immediately
after starting up in automatic mode, appropriate interlocks must be set up
according to how the plant is configured. The weighing of more than one
component in one scale will not be affected.
Function FC36 – ENABLE_CONDITIONS is created during the configuration
process, and describes the plant-specific dependences between the devices.
These interlock conditions determine the behavior of the plant every time a
recipe is processed, and they require careful consideration.
During configuration, the transition or start conditions are entered in FC36
ENABLE_CONDITIONS.
Example:
Two scales are each to be filled with 4 components in succession.
For this purpose each scale should be enabled. A wait time should be observed
between the individual dosings for each scale. The scales should work at the same
time.
The ExtEnd signal should be used to approve every dosing after it has been
completed.
Recipe composition:
Component 1 in scale 1 (Device 1)
Component 2 in scale 1 (Device 1)
Component 3 in scale 1 (Device 1)
Component 4 in scale 1 (Device 1)
Component 5 in scale 2 (Device 2)
BEGIN
NETWORK
TITLE =Enable scale 1
U T 1;
S "Db_Device_List".sDeviceRecord[1].sDevInput.boEnable;
U "Db_Device_List".sDeviceRecord[1].sDevStatus.boFinished;
S "Db_Device_List".sDeviceRecord[1].sDevInput.boExtEndSignal;
NETWORK
TITLE =Enable scale 2
U T 2;
S "Db_Device_List".sDeviceRecord[2].sDevInput.boEnable;
U "Db_Device_List".sDeviceRecord[2].sDevStatus.boFinished;
S "Db_Device_List".sDeviceRecord[2].sDevInput.boExtEndSignal;
During configuration, specific messages in a user program can be used to stop the
entire process.
The commands triggered by the function keys on the dosing status screen are
evaluated and executed by the Task Manager. During configuration, the triggering
of commands can be altered, e.g. by connections with interlocks in the plant
The following steps describe the procedure for configuring a third scale (logical
device number 3).
Note:
The number of scales can be extended to a maximum of 4 without any problem. If
there are even more scales involved when processing a recipe, then the Task
Manager device must be moved from number 5 to 11, for instance. This has the
effect of opening the way for additional scales (up to 10).
Hardware configuration:
Software configuration:
In the course of commissioning the scale with SIWATOOL FTA, the scale type
(DS4) must be set to SWE-Fill. In the DS7 interface parameters the SIMATIC S7
interface must also have the following setting:
Process value 1 – Net weight
Process value 2 - AWI status
From UDT12 generate an additional scales DB. The number of this DB should
follow on from the existing scale DB numbers.
In the symbols list define the symbolic name for the scales DB and the DB
instances of FB31 and FB41.
In OB35 (time), complete the call for the new scale
In FC20, configure the call for the SIWAREX FB41 function block. Use the same
calling system as for the two existing scales.
In FC20, configure the calls of COMMAND MANAGER FC30 and message block
FC1 in accordance with the existing system.
In FC35 CALL DEVICES store the call for the new scale.
In startup OB100 complete the delete procedures for the new scale.
In DB32 DB TASK PARAMETER LIST assign components to the new scale by
entering the new scale number.
In FC36 ENABLE CONDITIONS configure the release of the scale.
In Service Screen, Scale View permit selection of the new scale.
DB_TASK_INPUT_LIST
The task input list (recipe list) is used for entering recipes. First, a TASK INPUT
RECORD is defined, which is then used x times during the definition of the task
input list. X corresponds to the number of recipe lines. The number of the
component to be dosed is entered in the variable iTaskID, while the variable
iAutostate is not evaluated at this time in the task input list. The setpoint for the
entered component is entered in the variable rSetValueREAL. The variable
tSetValueTIME is not evaluated at this time.
Next, the DB TASK INPUT LIST is defined. Using variables iNumb and
sTaskInDef, the number of recipe lines (number of TASK INPUT RECORDs) is
defined. Note that the number of recipe lines in the task input list must be the same
as the number of recipe lines in the following DB_ACTUAL_TASK_LIST.
//--------------------------------------------------------------
// Definition of DB task input list
//--------------------------------------------------------------
// ** DB_TASK_INPUT_LIST **
DATA_BLOCK DB 30
TITLE = TaskInputList
FAMILY : Siwarex
NAME : MScale
VERSION : 1.1
STRUCT
iOffset : INT := 30; // Offset 1. data record
iLen : INT := 12; // Data record lenght
iNumb : INT := 10; // Number of data records
iInputTaskListID : INT := 1; // Input task list ID
iTempActRecord : INT := 1; // Temporary actual data record number
abFill : ARRAY [1 .. 2 ] OF BYTE ; // Filling area 1
sTaskListName : UDT 119; // Task list name
sTaskInDef : ARRAY [1 .. 10 ] OF UDT 100;
END_STRUCT ;
DB_TASK_ACTUAL_LIST
The task actual list (current recipe list = dosing status) is used when the recipe is
processed by the FC40 (Task Manager). Part of the task actual list is formed from
copying over the task input list. The list may only be copied over when no recipe is
being processed. First, a task record is defined, which is then used x times during
definition of the task actual list. X corresponds to the number of recipe lines, and
must be the same as in the task input list.
//--------------------------------------------------------------
// Definition of DB actual task list
//--------------------------------------------------------------
/ ** DB_TASK_ACT_LIST **
DATA_BLOCK DB 31
TITLE = ActTaskList
FAMILY : Siwarex
NAME : MScale
VERSION : 1.1
STRUCT
iOffset : INT := 38; // Offset 1. data record
iLen : INT := 40; // Data record lenght
iNumb : INT := 10; // Number of data records
iInputTaskListID : INT := 1; // Actual Task List ID
iTempActRecord : INT ; // Temporary actual data record number
iOffTaskOut : INT := 2; // Offset to Task_Out
iOffTaskPara : INT := 4; // Offset to Task_Basic_Para
iOffTaskDef : INT := 16; // Offset to Task_Input_Record
iOffTaskAct : INT := 28; // Offset to Task_Act_Values
abFill : ARRAY [1 .. 2 ] OF BYTE ; // Filling area
sTaskListName : UDT 119; // Task list name
sTaskRecord : ARRAY [1 .. 10 ] OF UDT 101; // data records for tasks
END_STRUCT ;
BEGIN
END_DATA_BLOCK
DB_TASK_PARAMETER_LIST
The task parameter list is used for managing the material data. Each component is
described in a data structure. A parameter record for the component parameter is
made up hierarchically from several UDTs. The number of components is specified
when the task parameter list DB is created. Each component is assigned when a
specific scale is configured. A decision must therefore be made during
configuration about how many components are needed per scale.
N.B.: the first 3 records form a reserve in the data block.
//--------------------------------------------------------------
// Definition of DB task parameter list
//--------------------------------------------------------------
// ** DB_TASK_PARA_LIST **
DATA_BLOCK DB 32
TITLE = TaskParaList
FAMILY : Siwarex
NAME : MScale
VERSION : 1.1
STRUCT
iOffset : INT := 14; // Offset 1. data record
iLen : INT := 50; // Data record lenght
iNumb : INT := 23; // Number of data records
iTaskParaListId : INT := 1; // Task para list ID
iTempActRecord : INT ; // Temporary actual data record number
iOffParaBits : INT := 12; // Offset to control bits
iOffDosingPara : INT := 14; // Offset to Task_Para_Record
DB_DEVICE_LIST
The DB DEVICE LIST is a table in which the current statuses of scales and/or
logical devices are managed.
In the system's as-delivered state the following configuration is stored:
Scale 1 is Device 1
Scale 2 is Device 2
The Task Manager program is device 5
Devices 3 and 4 are unassigned.
Note:
If more than 4 scales are to be involved with a recipe (task input list), then the task
manager should be assigned to a logical device, e.g. device no. 10.
//--------------------------------------------------------------
// Definition of DB Device record
//--------------------------------------------------------------
// ** DB_DEVICE_LIST **
DATA_BLOCK DB 34
TITLE = DevIO
FAMILY : Siwarex
NAME : MScale
VERSION : 1.1
//KNOW_HOW_PROTECT
STRUCT
iOffset : INT := 12; // byte-Offset 1. record
iLen : INT := 14; // record lenght
iNumb : INT := 5; // number of records
iReserve : INT ; // reserve
iTempActRecord : INT := 1; // temporary actual data record number
abFill : ARRAY [1..2] OF BYTE ; // filling area
sDeviceRecord : ARRAY [1..5] OF UDT 112; // device data record
END_STRUCT ;
DB_DEVICE_NAMES, DB_COMPONENT_NAMES
Names can be assigned to the devices and components. These names are
indicated on the corresponding screens. However, they have no significance as far
as sequence control is concerned.
// ** DB_DEVICE_NAMES **
DATA_BLOCK DB 38
STRUCT
iOffset : INT := 10; // byte-Offset 1. record
iLen : INT := 18; // record lenght
iNumb : INT := 5; // number of records
iReserve : INT ; // reserve
iTempActRecord : INT := 1; // temporary actual data record number
sDeviceName : ARRAY [1..5] OF UDT 119; // device name
END_STRUCT ;
BEGIN
END_DATA_BLOCK
// ** DB_COMP_NAMES **
DATA_BLOCK DB 39
TITLE = CompName
FAMILY : Siwarex
NAME : MScale
VERSION : 1.1
STRUCT
iOffset : INT := 10; // byte-Offset 1. record
iLen : INT := 18; // record lenght
iNumb : INT := 23; // number of records
iReserve : INT ; // reserve
iTempActRecord : INT := 1; // temporary actual data record number
sResName : ARRAY [1..3] OF UDT 119; // component name
sCompName : ARRAY [1..20] OF UDT 119; // component name
END_STRUCT ;
BEGIN
END_DATA_BLOCK
The symbol list provided with the system contains symbolic representations of the
programs and data ranges used.
INDW VAT 4
SET_CLK SFC 0 SFC 0 Set System Clock
Sft FB 41 FB 41
STEPS VAT 2
STP SFC 46 SFC 46 Change the CPU to STOP
UDT COMMAND STATUS UDT 1 UDT 1
Udt_Decice_In UDT 113 UDT 113 Input signals for device
The indication words indicate configuration errors, and can appear during
configuring and testing. Once the project has been commissioned these texts are
no longer of any significance to the operator.
5.4 Messages
Although the message programs from the free package "Getting started" (FB1 and
FC1) are not part of the SIWAREX MULTISCALE software, they are used here for
generating messages from all used scales.
The messages for a scale are decoded with the FC1 and passed onto the FB1
program for alarm generation with ALARM_S.
The alarm generation from the package "Getting started" is based on the
systematics of the ALARM_S components SFC18 and SFC19. In the scope
available here the scale alarms are monitored, the monitoring of the indication
The project has been created for TP270B. When converting to OP/MP 370, the
saved weight output in the Scale View screen must be deleted and reconfigured
(screen with the calibratable weight output).
The systematic structure of the screens for the first 2 scales must be continued in
the extension for further scales. The variables already available for 2 scales must
be created for further scales.
The variables which are multiplexed can be used for further scales from the
beginning.
If the recipe length is increased - for instance from 10 to 20 lines - then a new
screen must be configured as the second recipe page. The data blocks should be
extended before the screens are configured so that the variables can be linked
symbolically.
6 Technical Data
You can obtain information on add-on modules for SIWAREX MULTISCALE from
Ingenieurbüro Kaszkin www.ib-kaszkin.de.