SICAM 230 Manual: Allocations
SICAM 230 Manual: Allocations
Allocations
v.7.20
©2015 Ing. Punzenberger COPA-DATA GmbH
Distribution and/or reproduction of this document or parts thereof in any form are permitted solely
with the written permission of the company SIEMENS. Technical data is only used for product
description and are not guaranteed qualities in the legal sense. Subject to change, technical or
otherwise.
SICAM 230
Contents
2. Allocations .................................................................................................................................. 4
3
SICAM 230 Welcome to SIEMENS help
GENERAL HELP
If you cannot find any information you require in this help chapter or can think of anything that you
would like added, please send an email to [email protected]
(mailto:[email protected]).
PROJECT SUPPORT
You can receive support for any real project you may have from our Support Team, who you can contact
via email at [email protected] (mailto:[email protected]).
If you find that you need other modules or licenses, our staff will be happy to help you. Email
[email protected] (mailto:[email protected]).
2. Allocations
Allocations make it possible to place the current value of a variable onto a second variable within or
without the driver.
In
License information
4
SICAM 230 Allocations
SICAM 230 it is possible to write values from the controller directly into a SQL database or to write value
changes from one driver to another driver when they occur. You can also make cross-project allocations.
Attention: Cross-project allocations are executed only after all projects have been loaded.
TRANSFER
An allocation transfers value, state and time stamp of the source variable to the target variable.
Note: At the moment state and time stamp can only be processed by the following drivers:
Internal driver
SQL driver
The signal resolution should therefore have the same limits for both variables (overflow behavior).
The transfer of the value occurs on a vale change: Whenever the source variables value is changed, the
value of the target variable is changed as well. Should the value of the target variable be changed
independently from that of the source variable, then the target variable has the different value as long
as the value of the source variable does not change.
Information
Allocations to Internal variables are also only carried out on the server.
5
SICAM 230 Engineering in the Editor
3. select the desired action from the context menu or the tool bar, e.g. New allocation
4. in the properties window the properties of the new allocation are displayed and can be edited
an unique name
a source variable
a target variable
When selecting property Source variable or Target variable the corresponding variable list
for selecting the desired variable is displayed. Each variable of one of each driver can be selected as a
source. The target variable must be readable/writeable.
Each value change to the source variable is transmitted to the target variable of the allocation.
The context menu of the detailview of the Project Manager allows to cut, copy, insert or delete existing
allocations.
6
SICAM 230 Trigger variables and trigger type
CONTEXT MENU
Cut Copies the selected entries to the clipboard and deletes them from
the list.
Paste Pastes the contents of the clipboard. If an entry with the same name
already exists, the content is pasted as "Copy of...".
Edit selected cell Opens the selected cell for editing. The binocular symbol in the
header shows which cell has been selected in a highlighted line. Only
cells that can be edited can be selected.
7
SICAM 230 Trigger variables and trigger type
defined Edge The assignment is only executed if the trigger variable undergoes a
value change from 0 to 1. Only a positive edge of the bit variable
leads to the assignment being released. The assignment is no longer
instigated by a change to the value of the source variable.
defined Gage The assignment is always carried out as long as the trigger variable
has the value 1. Each time the value of the source variable changes,
the assignment is activated and the value is written to the target
variable. This assignment remains active until the value of the trigger
variable changes back to 0.