Professional Documents
Culture Documents
Simit Enus En-Us
Simit Enus En-Us
Basics of SIMIT 1
Couplings 2
SIMATIC
Simulation model 3
SIMIT Simulation Platform (V10.0) 4
Automatic model creation
Scripts 6
Libraries 8
06/2018
A5E44876196-AA
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this
publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Security information
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. Systems, machines and components should only be connected to the
enterprise network or the Internet if and to the extent necessary and with appropriate security
measures (e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into
account. You can find more information about industrial security on the Internet (http://
www.siemens.com/industrialsecurity).
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends applying product updates as soon as they are available and
always using the latest product versions. Using versions that are obsolete or are no longer
supported can increase the risk of cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed (http://www.siemens.com/industrialsecurity).
What's new?
SIMIT V10.0
Compared with the previous version V9.1, version V10.0 includes the following enhancements
or changes:
● New license model
A license based on the number of simulation tags in a simulation project replaces the
previous product versions, SIMIT Standard, SIMIT Professional and SIMIT Ultimate.
Licenses are managed on a Wibu dongle.
● Changes in DEMO mode
You start the DEMO version by double-clicking on the screen shortcut SIMIT SP Demo. The
DEMO version corresponds to the range of functions from SIMIT version "S".
– StorageTankLiquid
Licensing
License model
Simulation tags are the basis of the SIMIT license model. Simulation tags are calculated based
on the total number of inputs and outputs as well as the state variables of all components used
in the project. Because an implicit signal interconnection between two couplings takes on the
function of a diagram in which these signals are connected by means of a component with at
least one input and one output, such implicit interconnections in couplings are counted as two
simulation tags.
The following table shows the available SIMIT versions:
Additional licenses
Additional licenses are required for the following:
● An upgrade to a new version of SIMIT
● Additional libraries (CHEM-BASIC, FLOWNET or CONTEC)
● Component Type Editor (CTE)
● SIMIT Virtual Controller (VC)
Behavior in SIMIT
Select the size variant when SIMIT starts up. You can also change the size later with Portal view
> Start > Size variant.
The status bar shows the percentage of permitted simulation tags included in your simulation
project.
Introduction
SIMIT directly accesses the dongle when it is inserted into the local computer.
If the dongle is inserted in a computer in the network, you must set up the access to the dongle.
To do so, use the CodeMeter program on the server and the local computer.
Requirement
● The dongle is not inserted in the local computer but in a computer in the network.
Procedure
To open the help, follow these steps:
1. Go to "Start > CodeMeter > CodeMeter Control Center".
The "CodeMeter Control Center" opens.
2. Click on "WebAdmin".
3. Click on the "?" icon.
The "CodeMeter User Help" opens.
4. Execute the steps listed above under "Server access" and under "License access
authorizations".
Result
SIMIT accesses a license on a dongle that is inserted in a computer in the network.
Preface .........................................................................................................................................................3
1 Basics of SIMIT ..........................................................................................................................................21
1.1 Operating principle .................................................................................................................21
1.2 DEMO mode ..........................................................................................................................21
1.3 Starting SIMIT ........................................................................................................................23
1.4 The SIMIT graphical user interface ........................................................................................25
1.5 Creating a simulation .............................................................................................................27
1.5.1 Structure of a simulation ........................................................................................................27
1.5.2 Visualizing a simulation..........................................................................................................29
1.5.3 Visualizing coupling signals ...................................................................................................32
1.6 Simulation ..............................................................................................................................35
1.6.1 The states of a simulation ......................................................................................................35
1.6.2 Simulation operator control and monitoring ...........................................................................38
1.6.2.1 Actions during ongoing simulation .........................................................................................38
1.6.2.2 Display of the simulation load ................................................................................................39
1.6.2.3 Changes in a simulation project while a simulation is running ...............................................41
1.6.3 Settings for simulation............................................................................................................42
1.6.3.1 Operating modes....................................................................................................................42
1.6.3.2 Time slices .............................................................................................................................46
1.6.3.3 Speeding up and slowing simulation......................................................................................47
1.6.3.4 Adjustable timeout times ........................................................................................................48
1.7 Distributed simulation.............................................................................................................49
1.7.1 Method of operation of the distributed simulation ..................................................................49
1.7.2 Configuration of a distributed simulation ................................................................................50
1.7.3 Data exchange in a distributed simulation .............................................................................51
1.7.4 Setup firewall..........................................................................................................................52
1.7.5 Create screen link "SIMIT Client" ...........................................................................................53
1.7.6 Start distributed simulation.....................................................................................................54
1.7.7 Changing distributed simulation on a client PC......................................................................55
2 Couplings....................................................................................................................................................57
2.1 Coupling concept ...................................................................................................................57
2.1.1 Couplings in the SIMIT architecture .......................................................................................57
2.1.2 Couplings to SIMATIC PLCs..................................................................................................59
2.2 Coupling editor .......................................................................................................................61
2.3 Creating a HWCN export file..................................................................................................62
2.4 Deactivating couplings ...........................................................................................................63
2.5 SIMIT Unit ..............................................................................................................................64
2.5.1 Operating principle of the SIMIT Unit coupling.......................................................................64
2.5.2 Supported PROFIBUS DP configurations..............................................................................66
8.2.5.2 Fittings..................................................................................................................................606
8.2.5.3 Graphics...............................................................................................................................612
8.2.5.4 Heatexchanger.....................................................................................................................613
8.2.5.5 Measurements .....................................................................................................................627
8.2.5.6 Mixing apparatuses ..............................................................................................................637
8.2.5.7 Pump....................................................................................................................................640
8.2.5.8 Separators............................................................................................................................645
8.2.5.9 System .................................................................................................................................675
8.2.5.10 Tanks ...................................................................................................................................682
8.2.5.11 Valves ..................................................................................................................................703
8.2.6 Components in FLOWNET library........................................................................................713
8.2.6.1 General components............................................................................................................713
8.2.6.2 Measuring components........................................................................................................725
8.2.6.3 Component types for "water/steam" medium .......................................................................731
8.2.6.4 Component types for liquid medium.....................................................................................748
8.2.6.5 Component types for gas medium .......................................................................................760
8.2.7 Creating your own component types for flownets ................................................................773
8.2.7.1 Topological properties..........................................................................................................773
8.2.7.2 Connection to the solution procedure ..................................................................................776
8.2.7.3 Constants and functions.......................................................................................................783
8.2.7.4 Initializing FLOWNET simulations........................................................................................788
8.3 CONTEC library ...................................................................................................................788
8.3.1 Introduction ..........................................................................................................................788
8.3.2 Material handling simulation.................................................................................................789
8.3.2.1 Principles of conveyor technology simulation ......................................................................791
8.3.2.2 Modeling of the objects ........................................................................................................792
8.3.2.3 Modeling the conveyor system network ...............................................................................794
8.3.2.4 Special features of conveyor technology simulation ............................................................797
8.3.2.5 Scalability .............................................................................................................................799
8.3.2.6 Generating the simulation of drives and sensors .................................................................802
8.3.3 Components of the CONTEC library....................................................................................807
8.3.3.1 Topological connector in the CONTEC library .....................................................................807
8.3.3.2 Component types for conveyor systems with vehicles.........................................................808
8.3.3.3 Component types for non-vehicular conveyor systems ......................................................823
8.3.3.4 Component types for simulating objects ..............................................................................856
8.3.3.5 Component types for simulating identification systems .......................................................862
8.3.4 Creating custom component types for material handling simulation....................................892
8.3.4.1 Topological properties..........................................................................................................893
8.3.4.2 Connection to the solution procedure ..................................................................................896
8.3.4.3 System functions..................................................................................................................904
8.3.4.4 System variables..................................................................................................................913
9 Menus and dialog boxes...........................................................................................................................915
9.1 Menus ..................................................................................................................................915
9.1.1 Portal view > Start ................................................................................................................915
9.1.2 Portal view > Couplings........................................................................................................916
9.1.3 Portal view > Simulation model ............................................................................................916
9.1.4 Portal view > Automatic model creation ...............................................................................916
9.1.5 Portal view > Diagnostics & visualization .............................................................................917
9.1.6 Project > New project ... .......................................................................................................918
9.1.7 Project > Open... ..................................................................................................................919
9.1.8 Project > Close.....................................................................................................................919
● Snapshots
Snapshots cannot be taken in DEMO mode.
● Simulation process
In DEMO mode, the simulation can only run in real time. It cannot run faster or slower.
● Number of virtual controllers
You can run a maximum of 32 virtual controllers per SIMIT system.
● Size variant
You can only use the size variant S in DEMO mode.
The clear layout of the portal view helps you to quickly become familiar with SIMIT. The most
important basic functions can be selected directly:
● Manage projects
● Create couplings
● Create simulation models
● Automatic data import from different file formats
Getting started
After opening, creating or retrieving a project, the "Getting started" section opens. This is where
you can add the basic objects that are required for the function of a SIMIT project.
● Add coupling
● Add chart
● Generate charts automatically
You can perform these steps here or go to the project view to continue editing the project and
start the simulation.
① Menu bar and Access to SIMIT functions. Further functions are available in the short‐
toolbar cut menus in the project navigation.
② Task cards Objects such as library components, controls and graphic objects that
can be used in the editor currently open are listed here. These objects
are sorted in task cards.
③ Work area This is where the editors are opened for editing.
④ Project naviga‐ The current project is displayed here in a tree view.
tion
⑤ Property view The properties of the selected object are displayed here.
⑥ Editor bar and Here, you can switch between open editors and the portal view. If nec‐
status bar essary, information on the current status of SIMIT is displayed here.
All editors are opened in the work area. Task cards are provided specifically for each editor. The
work area can be divided in order to open two editors side-by-side or underneath one another
in the work area.
The following functions can be performed using the window buttons of an editor:
Project navigation
Projects are managed in the project navigation. A SIMIT project is divided into the following tree
nodes, whereby a project must not contain all of the objects listed here:
"Lists" folder: This folder contains the "New list" function and is the
storage location for existing material lists.
This folder is only relevant if the "CONTEC" library has been installed.
You can find additional information on this in section: Modeling of the
objects (Page 792).
"Snapshots" folder: Folder for storing snapshots of the simulation
When simulation is running, the folder also contains the "New snap‐
shot" function.
You can find additional information on this in section: Actions during
ongoing simulation (Page 38).
Tree node for "Find & replace" function Searches can be made for
signals, components, connectors, and graphic texts.
You can find additional information on this in section: Find & replace
(Page 289).
Tree node for performing the consistency check. The consistency
check verifies the project for formal errors.
You can find additional information on this in section: Consistency
check (Page 294).
Tree node for starting simulation.
You can find a brief description of these elements below. For more information, please see the
links.
● Chart
The chart contains the simulation model. Components, controls and connections are
graphically displayed. Charts are created and edited in the chart editor. A simulation model
can consist of multiple charts.
You can find additional information in section: Chart editor (Page 217).
The figure below shows an example of a chart with components, connections and controls:
Note
The coupling configuration must first be saved before a signal can be extracted from it.
Controls are ready-to-use objects for entering or displaying signals. They just need to be
connected to the required signal.
Graphics are created individually. Graphics can be static or animated.
Controls
Controls are categorized by signal input or display and by data type. The following controls are
available:
Analog display Analog, in‐ Signal display Analog display (Page 555)
teger
Digital display Analog, in‐ Signal display Digital display (Page 557)
teger
Bar graph display Analog, in‐ Signal display Bar graph display (Page 559)
teger
Button with image Binary Signal input Pushbutton with image (Page 561)
Switch with image Binary Signal input Switch with image (Page 563)
Step switch with image Integer Signal input Step switch with image (Page 565)
Graphics
You use graphics to display signals with an individual view. Static graphics specify a particular
display; animated graphics change within the simulation in size, color and position in line with
their current state.
6. Set appropriate filter settings in the coupling window and select the required signal with a
click of the mouse.
To select multiple signals, press <Strg> (individual selection) or <Shift> (area selection).
7. Select the " " symbol in the first column of the coupling window.
8. Drag-and-drop the selected signals to the chart as shown in the figure below:
A switch is generated for signals with the data type "Binary", and a digital input for all other
signals, as a control in the coupling.
Dragging coupling signals from the "Signals" task card to the chart
You can alternatively also drag coupling signals from the "Signals" task card to charts.
Follow these steps:
1. Open the chart in the work area.
2. Open the "Signals" task card.
All signals saved in the project are available on this task card.
3. To select signals, set corresponding filters for the signal list. You can find additional
information in section: "Signals" task card (Page 233).
4. Select the signals from the list and drag-and-drop them to the chart as shown in the figure
below:
1.6 Simulation
2IIOLQH
6LPXODWLRQ!6WDUW
6LPXODWLRQ!,QLWLDOL]H
6LPXODWLRQ!(QG
6723 67$57
6LPXODWLRQ!3DXVH 6LPXODWLRQ!6WDUW
6LPXODWLRQ!(QG
5XQQLQJ
Initializing simulation
Simulation is initialized with the menu command "Simulation > Initialize".
You can run simulation initialization before starting a simulation. The state changes to
"Paused". The initialization runs the consistency check; messages are displayed in the event
of an error. You can find additional information on this in section: Consistency check
(Page 294).
The "Single step" function can be executed by an initialized simulation.
Simulation starts
Simulation is started with the following commands.
● With the " " symbol in the toolbar
● With the menu command "Simulation > Initialize".
● With the project navigation by double-clicking on
Once simulation has been started, SIMIT changes the color scheme of the interface from blue
to orange; the state changes to "Running".
You can find additional information on running simulation in: Actions during ongoing simulation
(Page 38).
Stopping simulation
Simulation is ended with the following commands:
● With the " " symbol in the toolbar
● With the menu command "Simulation > End".
The state changes to "Offline" and the color scheme of the interface changes back to blue.
Load fluctuations
The load value is not always constant. A fluctuating load can be caused by:
● The simulation model itself can create more load in each calculation step due to the
configuration
● A time slice is interrupted by a time slice with a higher priority.
● Other applications are running in the background in addition to SIMIT
● Internal processes in both the operating system and in the .NET environment used by SIMIT
may delay the simulation calculation
In order to keep the graphical representation of the interface calm, the load values are
smoothed over several increments.
Note
If the load value always jumps back and forth between two values, the problem may be that the
processor of your computer keeps changing the clock frequency for energy saving reasons.
You can avoid this by altering the system settings of your computer, for example. Select
"Control panel > Power Options > Power plan > Advanced power settings > High performance".
Note
The Windows Task Manager is not suitable for evaluating the simulation load. On the one hand,
the distribution of the simulation model on multiple processors or cores has to be taken into
consideration; on the other hand, the task manager only indicates the computing power but not
whether the configured cycle time cannot be met due to communication delays.
Note
If the simulation load is too high, you can access information on the cause with the
"SimulationLoad" component.
You can find additional information on the component in: SimulationLoad (Page 449)
You can open charts in both project views, but for different purposes:
● If you are in the blue project view, charts are opened for editing. The changes that you make
take effect the next time the simulation is started or when you select the "Activate changes"
menu command.
● If you are in the orange simulation view, charts are opened for operation. Their content
corresponds to the simulation that is running and cannot be changed.
The same chart can be opened simultaneously in both modes. When the simulation ends, the
chart opened from the simulation tree closes automatically.
While the simulation is running, the following restrictions apply to using SIMIT:
● No new couplings can be created and existing ones cannot be deleted.
● Only implicit interconnections can be edited in the couplings.
● All functions of "Automatic modeling" are disabled.
Note
While the changes are activated, the simulation model does not process any values for some
time. During this time, I/O devices may not respond. The length of time depends on the size of
the simulation model.
If the current simulation state is transferred to the new configuration, the values can be
identified and assigned based on the signal name. Values for which there is no equivalent are
assigned initial values.
Activation does not include the values of parameters and defaults that are modifiable online; the
values from the simulation in progress are retained. Restart the simulation to enable these
value changes.
The simulation model and the couplings can be edited in the three different operating
modes asynchronous, synchronous and bus synchronous.
Which mode is appropriate depends on the project. It is set in the property view in the project
manager:
0RGHOO
.RSSOXQJ
2XWSXWVLJQDO ,QSXWVLJQDO
LVUHFHLYHG LVUHWXUQHG
If the model calculation or the data communication of couplings takes longer than half of the
cycle time, this time offset does not result in faster response time.
Note
The same value should be set for both the cycle time of the coupling (coupling cycle) and the
cycle time for the calculation of the simulation model (simulation cycle).
In the example below, both the automation system and the calculation of the model have a
cycle time of 100 ms. As the automation system and the simulation are not synchronized, their
timing is usually shifted with respect to each other. The simulation cycle takes no longer than
half the model calculation cycle:
6LPXODWLRQF\FOH
&RXSOLQJF\FOH
&RQWUROOHU
6LJQDOH[FKDQJH
&RXSOLQJPHPRU\
6LPXODWLRQPRGHO
7LPH
PV PV PV PV
① At this time, the automation system has finished its calculation cycle. Additional signals are
available at the outputs of the automation system.
② The output signals of the automation system are applied to the SIMIT coupling memory.
Here they are available for the calculation of the model.
③ The calculation of the model is triggered again.
④ End of the model calculation cycle. The calculated input signals for the automation system
are now available in the coupling memory.
⑤ With the next clock pulse of the coupling, these input signals are transferred to the controller.
⑥ If the controller only evaluates its inputs at the start of a cycle, the transferred input signals
are only used in the control program now. This means the reaction of the simulation does not
take place until two control cycles later.
0RGHOO
.RSSOXQJ
2XWSXWVLJQDO ,QSXWVLJQDO
LVUHFHLYHG LVUHWXUQHG
This results in better response times with short cycle times. However, each module and each
coupling can block the entire simulation execution.
Example
In the example shown here, the cycle time is 2 ms and a time slice of the project must be set
to 2 ms.
In the top part of the figure you can see how long PLCSIM Advanced, SIMIT and MCD need for
their calculations. Only when all three calculations are complete and the results have been
exchanged do the calculations for the next cycle start. Even if the calculations in the simulation
take longer than the cycle time of 2 ms, the calculation time in the real plant always corresponds
to the set cycle time.
In the bottom part of the figure you can see the timing of the CPU, drive and axis in the real plant.
&38
'ULYH
3ODQW
$[LV
Definition
Simulations are calculated cyclically. The cycle time specifies the time frame in which the
calculations are to be performed and data is to be exchanged. The cycle time is set by means
of one of eight available time slices. The absolute cycle time for a time slice is set in the project
manager and is valid for the entire project. The minimum cycle time that can be set is 1 ms.
You set the time slice and the sub-time slice of a chart or chart folder using the shortcut menu
in the "Set time slice" dialog box.
Maximum acceleration is limited in such a way that the shortest cycle time of the project is at
least 1 ms taking into account the acceleration. After the end of the time shift, the time is
synchronized with the computer time again.
This means acceleration may not be possible depending on the cycle time. Only suitable values
are offered for selection.
Note
Time response
Timer OBs in the virtual controller and timer functions that are dependent on timer OBs in the
virtual controller may result in an irregular time response.
Method of operation
The complexity of the simulation project is limited by the computing power of the simulation PC.
To realize complex simulation projects with SIMIT, distribute a simulation project to up to 16
client PCs. You control the simulation centrally from the master PC.
3URFHVV 3URFHVV
VLPXODWLRQ VLPXODWLRQ
&OLHQW &OLHQW
7&3,3
0DVWHU
3URFHVV
VLPXODWLRQ
Typical scenarios for the use of distributed simulation are, for example,
● Plant components act mostly independent of one another
● Little or no time-critical data exchange between the plant components
● Power plant with multiple blocks
● Manufacturing process with multiple lines
7&3,3 7&3,3
7&3,3 7&3,3
① When you start the simulation on the master PC, you also start the partial simulations on the client PCs.
② To change a subproject on a client PC, disable the remote control of the client PC by the master PC. Then change
the model on the client PC.
③ When you subsequently restore the remote control of the client PC by the master PC, all partial simulations are once
again synchronous again.
See also
Changing distributed simulation on a client PC (Page 55)
Start distributed simulation (Page 54)
Distributed simulation with data exchange between client PCs and master PC
If your simulation cannot be completely subdivided into independent partial simulations, use
the distributed simulation with data exchange. Divide your project into subprojects so that the
partial simulations exchange as little data as possible.
Use the OPC DA coupling, for example, for the data exchange. In the example below, the
master PC of the distributed simulation is also the OPC DA server. The client PCs of the
distributed simulation are the OPC DA clients.
3URFHVV 3URFHVV
VLPXODWLRQ VLPXODWLRQ
&OLHQW &OLHQW
23&FOLHQW 23&FOLHQW
7&3,3
0DVWHU
23&VHUYHU
3URFHVV
VLPXODWLRQ
Figure 1-1 Distributed simulation with data exchange between client PCs and master PC
Introduction
Set the firewall to ensure that SIMIT SP can establish a connection to the following systems:
● Further SIMIT SP instances in a distributed simulation
● Distributed Virtual Controllers
● Third-party systems which establish a connection to SIMIT SP using a simulation controller
(RCI)
NOTICE
Read the security notes included in the foreword
Changes to the firewall may influence the security of your system!
Contact, if necessary, your system administrator before performing the steps described in the
following.
Requirement
● SIMIT has been installed.
● All nodes are located within the same network.
Procedure
Proceed as follows to set up the firewall:
1. Open the "Windows Defender Firewall with extended safety", for example, by entering
"wf.msc" in the system prompt and confirming with "Enter".
2. Click on “Incoming rules”.
3. Double-click "SIMIT-CS Manager".
The “Properties of SIMIT CS Manager" windows opens.
4. Select the “Area” tab.
5. Under “Remote IP address”, select “Arbitrary IP address”. Alternatively, add the IP
addresses of the systems involved to the list of approved remote IP addresses.
6. Confirm with "OK".
Result
The firewall has been set such that SIMIT SP can set up a connection to other systems.
See also
Preface (Page 3)
Introduction
To start SIMIT in client mode, create a screen link with a corresponding transfer parameter.
Syntax of the transfer parameter: /[M|m]:<IP address>:<Port>
● /M: The operator of the client PC can disable the remote control.
● /m: The operator of the client PC cannot disable the remote control.
● <IP address>: IP address of the master PC
● <Port>: Port number of the master PC, default value: 50800.
If an administrator has changed the default port, you can locate the current port on the
master PC in the registry under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
\Siemens\SIMIT\8.0] in the "uri" key.
Example for a complete transfer parameter:
Requirement
● SIMIT is installed.
● The firewall configuration of the master PC permits incoming connections at the port
number.
Procedure
To create a "SIMIT Client" screen link, follow these steps:
1. Copy the link "SIMIT SP" to the screen.
2. Add the transfer parameter in the properties of the copied link.
3. Rename the link to "SIMIT Client".
Result
The "SIMIT Client" screen link has been created.
Requirement
● The master PC and the client PCs are located in the same network.
● A project with the same name is stored on the master PC and the client PCs under the same
local path.
● The screen link (Page 53) "SIMIT Client" has been set up on all client PCs.
Procedure
To start a distributed simulation, follow these steps:
1. Start SIMIT on the master PC.
2. On the client PCs, start SIMIT in client mode.
3. Open the project on the master PC.
4. Start the simulation on the master PC.
Result
The simulation runs on the master PC and on the client PCs.
See also
Configuration of a distributed simulation (Page 50)
Introduction
No model changes are possible on the client PC during an ongoing distributed simulation. To
change the model, interrupt the connection between the client PC and the master PC.
Requirement
● A distributed simulation runs on the master PC and on the client PCs.
● The client PC was started with the transfer parameter "/M".
Procedure
To change a distributed simulation on the client PC, follow these steps:
1. Deactivate the "Remote control active" option in the project properties.
The connection to the master PC is disconnected. The simulation on the client PC initially
continues.
2. Change the model.
3. Start the simulation with your changes.
4. When the simulation can be run, bring the simulation on the client PC into the same state as
the simulation on the master PC.
5. Activate the "Remote control active" option in the project properties.
Result
The client PC once again runs under the control of the master PC.
See also
Configuration of a distributed simulation (Page 50)
Introduction
A coupling is an interface between SIMIT and a coupling partner, for example, an automation
system. A coupling has the following tasks:
● Signal exchange with the coupling partner
The input/output signals (I/O signals) of the coupling partner are exchanged with SIMIT over
the coupling.
● Coordination of signal exchange between SIMIT and the coupling partner
Types of coupling
There are three different types of coupling in SIMIT:
● Coupling with a real SIMATIC controller
● Coupling with an emulated SIMATIC controller
● Coupling with an external partner
Coupling with a real SIMATIC Coupling with an emulated SIMATIC Coupling with an ex‐
controller controller ternal partner
SIMIT Unit PRODAVE Virtual con‐ PLCSIM PLCSIM –
troller Advanced
Simulation of bus behavior Yes No No No
Simulation of isochronous No No Yes No1
mode
Access to the process im‐ Yes Yes No
age
Use of hardware configu‐ Yes No Yes No No No
ration data from STEP 7
Import and export of sig‐ Yes Yes Yes2
nals
1
The MCD coupling supports isochronous mode.
2
Depending on the external coupling partner
Each coupling has its own configurator for creating and editing the coupling.
Note
A maximum of 16 external couplings can be used in a SIMIT project, regardless of the coupling
type.
3URMHFWPDQDJHPHQW
&RQWUROV\VWHP
&RPSRQHQWV 0RGHO &RGH 6LPXODWLRQ
JHQHUDWRU PRGHO
&RXSOLQJ
FRQILJXUDWRUV
6,0,78QLW 9LUWXDOFRQWUROOHU
&RPPXQLFDWLRQ
&RXSOLQJV
LQUXQQLQJ57
352'$9( 0&'
FRQILJXUDWLRQ
+DUGZDUH
3/&6,0$GYDQFHG 6KDUHGPHPRU\
3/&6,0 23&'$23&8$
&RXSOLQJSDUWQHU
A coupling provides the connection between the simulation model run by the control system
and the coupling partner.
● The interface to the simulation model
This interface is the same for all couplings. The simulation model therefore does not depend
on the type of coupling used. Couplings can therefore be interchanged within the simulation
model without having to be modified.
● The interface to the coupling partner
The interface must be configured once for each coupling. The interface is different for each
coupling.
Configuration of couplings
For signal exchange between the simulation model and an automation system, the coupling
must contain the following information:
● The information required to establish the connection
● Signals to be exchanged
This information is saved for each coupling with a configurator.
Introduction
SIMIT provides couplings with a SIMATIC controller such as S7-400 over PROFIBUS DP,
PROFINET IO or PRODAVE and a coupling to PLCSIM / PLCSIM Advanced and to SIMIT VC.
The data required for the configuration can be taken from the SIMATIC projects.
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'3VODYHV
"SIMIT Units" that simulate the field devices are used in SIMIT to do this. Such an SIMIT Unit
is connected to the PROFIBUS DP master or PROFINET IO controller of the control system in
the simplest configuration. The controller then communicates with this SIMIT Unit and with
SIMIT in the same way as in a real plant with the field devices. The SIMIT interface to the
SIMATIC controller is in this case the field bus cable.
You can find additional information on this under SIMIT Unit (Page 64).
Note
IP address space
SIMIT only supports PCS 7 projects with an IP V4 address space.
① Menu bar
The content of the menu bar depends on the coupling type. By default, the menu bar includes the commands for
importing and exporting signals. For further information, please refer to: Importing and exporting signals (Page 193)
② Input and output signals
Lists the signals with their associated parameters and properties separately by "Inputs" and "Outputs":
● You connect the signals under "Inputs" to the output connectors in the simulation model.
● You connect the signals under "Outputs" to the input connectors in the simulation model.
You can find information on editing signals in the coupling editor in: Signal basics (Page 182).
③ Property view
In the property view you edit the properties of a signal or those of the coupling you selected in the project tree.
The properties that are displayed depend on the type of coupling.
Introduction
To import stations from a STEP 7/PCS 7 project on a SIMIT PC on which PCS 7 is not installed,
generate a HWCNExport file from the STEP 7/PCS 7 project. To generate the HWCNExport
file, use the "HWCNExport" application that is by default installed with SIMIT.
Note
The "HWCNExport" application can be run without additional installation.
You can find the application in the Start menu "Start > All Programs >Siemens Automation >
SIMIT > Tools".
If you want to use this application on a PC without a SIMIT installation, copy the complete folder
to any location on the PC and start the "HWCNExport".
Requirement
● Creating an HWCNExport file for a virtual controller:
– STEP 7 up to V5.5 is installed.
● Creating an HWCNExport file for PLCSIM Advanced:
– STEP 7 (V14 SP1 to V15.1) is installed.
– TIA Portal Openness is installed.
– STEP 7 project is closed.
● .NET Framework 3.5 or higher is installed.
● There is a folder with the "HWCNExport" application.
Procedure
Proceed as follows to create an HWCNExport file:
1. Start the "HWCNExport" application.
2. To export the hardware configuration from a STEP 7 V5.5 project:
– Select the "STEP 7 V5.x" tab.
– Select the required STEP 7/PCS 7 project type.
– Select the STEP 7/PCS 7 project.
Result
The HWCNExport file is created in "*.XML" format.
See also
"Virtual controller import" dialog box (Page 929)
"PLCSIM Advanced import" dialog box (Page 928)
The coupling is then not enabled the next time simulation is started. All values for the signals
in this coupling are set to "0". There is no signal exchange.
This function is only available with the following types of coupling:
● SIMIT Unit
● PLCSIM
● PRODAVE
● OPC client
Function
SIMIT communicates with one or more bus systems over the "SIMIT Unit" coupling:
● PROFINET IO controller
● PROFIBUS DP master
The "SIMIT Unit" is used as a link for communication between the controller and SIMIT. The
SIMIT Unit maps the behavior of devices at the bus and enables the exchange of data between
the controller and SIMIT.
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'3VODYHV
352),%86'3
352),1(7,2
(WKHUQHW
352),1(7,2
6XEQHW 6XEQHW
Additional information
You can find more information on the SIMIT Unit on the Internet (https://
support.industry.siemens.com/cs/ww/en/view/109746192).
See also
Configuring a SIMIT Unit (Page 83)
Supported PROFIBUS DP configurations (Page 66)
Introduction
Typical PROFIBUS DP configurations that are supported by SIMIT are listed below. In the left
of the figure (see below), you can see the configuration of the automation system and on the
right the layout with SIMIT. The following examples of configurations with non-redundant
controllers are shown:
● A controller with a PROFIBUS DP line
● A controller with two PROFIBUS DP lines
● Two controllers, each with a PROFIBUS DP line
The following examples of redundant configurations are provided:
● A redundant controller with a redundant PROFIBUS DP line
● One redundant controller with Y-link
● Two redundant controllers, each with a PROFIBUS DP line configured at one end only
For all configurations, a mixed configuration of real and simulated PROFIBUS DP slaves is
possible.
Bus couplers can also be used, either as DP/DP couplers, as DP/PA couplers, or in redundant
configurations as a Y-link.
Fail-safe I/Os can also be simulated in redundant H/F systems.
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'3VODYHV
Note
In this configuration, only one channel of a two-channel SIMIT Unit is used.
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'3VODYHV
352),%86'3
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'3VODYHV
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'36ODYHV
352),%86'3
352),%86'3
(WKHUQHW
3URILEXV'36ODYHV
</LQN
</LQN
Two redundant controllers, each with a PROFIBUS DP line configured at one end only
352),%86'3
(WKHUQHW
352),%86'3
3URILEXV'3VODYHV
352),%86'3
Note
Note that the station must actually be configured at one end only in STEP 7.
See also
Redundant configurations (H systems) (Page 78)
Introduction
Typical PROFINET IO configurations that are supported by SIMIT are listed below. In the left
of the figure (see below), you can see the configuration of the automation system and on the
right the layout with SIMIT.
● A controller with a PROFINET IO line
● A redundant controller with a redundant PROFIBUS IO line
● One controller with Shared Device
● Ring topology
Note
The IP address of the SIMIT Unit and the IP addresses of the simulated PROFINET IO devices
must be located in different subnets.
Example:
● IP address of the SIMIT Unit: 192.169.xxx.yyy, subnet mask: 255.255.0.0
● IP address of a simulated PROFINET IO device: 192.168.xxx.yyy, subnet mask:
255.255.0.0
At least one digit of the first two segments of the IP address must be different.
352),1(7,2
352),1(7,2
(WKHUQHW
352),1(7,2VODYHV
352),1(7,2
352),1(7,2
(WKHUQHW
352),1(7,2VODYHV
352),1(7,2
(WKHUQHW (WKHUQHW
Ring topology
352),1(7,2
352),1(7,2
(WKHUQHW
352),1(7,2VODYHV
The figure below is a schematic representation of the necessary configuration settings in SIMIT:
352),1(7,2
(WKHUQHW
352),1(7,2VODYHV
6,0,781,7,3
3RUW
)LUVWGHYLFHDWSRUW
)LUVWGHYLFHSRUWDWSRUW
)LUVWGHYLFHDWSRUW
3RUW )LUVWGHYLFHSRUWDWSRUW
See also
Properties of the SIMIT Unit coupling (Page 96)
Redundant and fail-safe systems (Page 78)
Introduction
SIMIT supports the simulation of redundant systems (H-systems). In a connected redundant
system, all redundant diagnostic signals required are generated by the SIMIT Unit. This means
you can also switch your controller from master to standby and back. You can see whether or
not a slave is redundant under "H-system" in the slave property view.
DP/DP couplers can also be included as a Y-link in redundant systems. The coupling signals
of bus nodes that are connected behind the Y-link are also available in SIMIT in the same way
as the coupling signals of nodes that are connected directly to the redundant bus.
Note
The simulation of a redundant PROFINET system is only supported with SIMIT Unit PN 256.
Setup example
When you configure a coupling to a redundant system, one SIMIT Unit is required for each
redundant system. Two redundant systems are configured in the example below. Two lines are
configured at each redundant system, but the distributed I/O is only connected to one line each.
The following configuration is not permitted with only one SIMIT unit:
352),%86'3
352),%86'3
352),%86'3
(WKHUQHW
352),%86'3
3URILEXV'36ODYHV
352),%86'3
352),%86'3
352),%86'3
(WKHUQHW
(WKHUQHW 3URILEXV'36ODYHV
3URILEXV'36ODYHV
352),%86'3
All quality signals set to "1" are valid by default. To set a signal to "invalid", set the
corresponding quality signal to "0" and deselect the check box under "Quality bit" in the property
view. This can be used, for example, to test the reaction of your control program to signal
interference.
Note
After loading the interface module with a fail-safe configuration, the connected SIMATIC CPU
needs to be restarted.
Requirement
● SIMIT Unit can be accessed in the network.
● SIMIT is open.
Procedure
Follow these steps to configure a SIMIT Unit:
1. Select the "SU management" command from the "Options" menu.
The "SU management" dialog box opens. The system automatically searches for available
SIMIT units in the network.
2. Enter the following information for the SIMIT Unit:
– Name
– IP address
– Subnet mask
Result
The SIMIT Unit is configured. The configuration data are saved in the SIMIT Unit.
See also
Operating principle of the SIMIT Unit coupling (Page 64)
"SU administration" dialog box (Page 937)
Creating a coupling of the "SIMIT Unit" type (Page 85)
Introduction
If data for a device is already available in the delivered SIMIT software, it is shown in the "SU
Administration" as "System". If you import the GSD or GSDML files to a device, they are
displayed in the "SU mdministration" as "User". The "User" information generally takes
precedence over the "System" information.
Requirement
● SIMIT is open.
● Device description file is available.
Procedure
Follow these steps to import a device description file:
1. Select the "SU management" command from the "Options" menu.
The "SU management" dialog box will open. The system automatically searches for
available SIMIT units in the network.
2. Select the tab for importing a device description file.
3. Click on "Import" to open the device description data.
Result
The additional device information is imported and listed. The device information is saved on the
PC on which SIMIT is installed.
See also
"SU administration" dialog box (Page 937)
Configuring a SIMIT Unit (Page 83)
Requirement
● SIMIT Unit is configured.
● SIMIT is open.
● Firmware file is available.
Procedure
NOTICE
Damage of SIMIT Unit possible during firmware update
Observe the following rules for the duration of the firmware update:
● Do not switch off the SIMIT Unit.
● Do not restart the SIMIT Unit.
● Do not remove or connect any cables from or to the SIMIT Unit.
To ensure an uninterruptible power supply, connect the SIMIT Unit to a UPS.
Result
The firmware of the SIMIT Unit is updated. Once the firmware update is complete, update the
overview of SIMIT Units under "SU management".
See also
Configuring a SIMIT Unit (Page 83)
"SU administration" dialog box (Page 937)
Introduction
You can create a coupling of the "SIMIT Unit" type in a SIMIT project. You create "stations"
under the SIMIT Unit to which the hardware configuration of a station is imported from STEP 7.
Requirement
● Project is open in SIMIT.
Procedure
Follow these steps to create a coupling of the "SIMIT Unit" type:
1. Add a new coupling in the project tree under "Couplings".
The "Selection" dialog box opens.
2. Select the coupling type "SIMIT Unit".
Result
The "SIMIT Unit" coupling is created together with a station in the project tree.
See also
Configuring a SIMIT Unit (Page 83)
Requirement
● Project is open.
● Coupling of the "SIMIT Unit" type has been created.
● Hardware configuration from STEP 7 is available.
Procedure
Follow these steps to create a station:
1. Add a new station under "SIMIT Unit" in the project tree.
2. Open the station.
The "SU import" dialog box will open.
3. Configure the import of the stations from the hardware configuration.
Result
You can find the result after import of the hardware configuration in Importing hardware
configuration to station (Page 87).
See also
"SU Import" dialog box (Page 927)
Introduction
If STEP 7 and SIMIT are installed on different PCs, transfer the system data blocks with a
software package provided by SIMIT:
● UnlockHWConfig.exe
● CopyHWConfig.exe
Neither program requires installation and both can be accessed from anywhere. The programs
are saved in the following folders:
● SIMIT CD: "Support\Tools"
● PC with installed SIMIT: Windows start menu under "Siemens Automation > SIMIT > Tools"
67(3
WUDQVIHUULQJVGEILOHV
FRS\LQJVGEILOHV LPSRUWLQJVGEILOHV
UnlockHWConfig.exe
In STEP 7, the sdb files are by default deleted following compilation of the hardware
configuration. To prevent this permanently, launch the program "UnlockHWConfig.exe" once
on the STEP 7 PC. Note that you must run this program with administrator rights.
CopyHWConfig.exe
To copy the system data blocks, use the program "CopyHWConfig.exe". By default, the
following folders are set as source folders:
● STEP 7 V5.5 and later: Temporary STEP 7 storage folder
● STEP 7 V13 and higher: "C:\TIAExports\"
Note
Configuration in Run (CiR)
"Configuration in Run" is not supported by SIMIT. Import the system data blocks again if you
have changed the hardware configuration in STEP 7.
Introduction
The hardware configuration is imported straight from STEP 7 or from the copied system data
blocks. System data blocks are generated each time the hardware configuration is compiled in
STEP 7. Import the hardware configuration to the station in SIMIT again if you have changed
the hardware configuration in STEP 7.
STEP 7 version SIMATIC controllers supported Format of the system data blocks
V5.5 and higher 1
● S7-300 / S7-400 ● SDB
as of V13 (TIA Portal)2
● S7-300 / S7-400 ● SDB
● S7-1200 / S7-1500 ● OMS
1
Standard storage folder for system data blocks "<STEP7 installation folder> \S7Tmp\SDBDATA
\S7hwcnfx\DOWN\r00s0x"
2
Standard storage folder for system data blocks: "C:\TIAExports"
Requirement
● Coupling of the "SIMIT Unit" type has been created.
● Station has been created under the coupling.
● Station hardware configuration from STEP 7 is available.
● Hardware configuration in STEP 7 has been compiled and loaded.
● Station is open in the coupling editor.
Procedure
Follow these steps to import the hardware configuration to a station:
1. Open the dialog box for importing the hardware configuration in the Coupling Editor.
2. Select the source from which you want to import the hardware configuration.
3. If you import the hardware configuration from STEP 7 V5.5 and higher, also select the
configuration file in *.CFG format.
4. Select the devices.
5. Click "Import".
Result
The hardware configuration of the station is imported.
See also
Editing the signals of a coupling (Page 182)
Creating a station (Page 86)
Configuring the station (Page 90)
"SU Import" dialog box (Page 927)
Introduction
SIMIT supports simulation of shared devices.
Requirement
● Coupling of the type "SIMIT Unit" has been created.
● Station has been created under the coupling.
● Hardware configuration of the stations from STEP 7 exists.
● Station with the header data for the Shared Device is known.
● Hardware configuration is compiled and loaded in STEP 7.
● Station is open in the coupling editor.
Procedure
To import the hardware configuration for shared devices into a station, proceed as follows:
1. Import the hardware configuration of the CPU into the station without header data:
– In the coupling editor, open the dialog box for importing the hardware configuration.
– Select the source.
– When you import the hardware configuration of an S7-300 or S7-400, also specify the
configuration file.
– Select the devices.
– Click "Import".
The "Incomplete import of shared devices detected" message is displayed.
2. Import the hardware configuration of the CPU which contains the header data of the Shared
Device into the station:
– In the coupling editor, open the dialog box for importing the hardware configuration.
– Select the source.
– When you import the hardware configuration of an S7-300 or S7-400, also specify the
configuration file.
– Activate the "Additional information for Shared Devices" option.
– Select the devices.
– Click "Import".
Result
The hardware configuration of the station from STEP 7 is imported.
Introduction
The schematic diagram below shows what information is required for configuring a SIMIT Unit
in SIMIT:
&KDQQHO
352),%86'3
(WKHUQHW
Requirement
● Station has been created.
● IP address of the SIMIT Unit is known.
● Hardware configuration has been imported.
Procedure
Follow these steps to configure a station:
1. Double-click on the required station in the project tree under "Couplings > SIMIT Unit".
2. In the properties window, select the "time slice" of the station.
3. In the properties window, assign each master system to a SIMIT unit under "Station":
– Select the IP address of the SIMIT Unit.
– Select the channel of the SIMIT Unit to which the master system is connected.
4. Save the configuration.
Result
The station is configured. The figure below shows the assignment of a PROFIBUS master
system of a station to a SIMIT Unit:
See also
Loading configuration to station (Page 95)
Importing hardware configuration to station (Page 87)
Properties of the SIMIT Unit coupling (Page 96)
Alarms
In SIMIT, you can simulate alarms for the following levels of a station:
● PROFIBUS
Line, slave, module, channel
● PROFINET IO
Line, device, module, submodule, channel
You simulate alarms either in the properties of a station or with the "SetInterrupt" component.
Note
Response with migrated projects from SIMIT versions earlier than V10
To simulate alarms, import a current hardware configuration once.
6WDWLRQ
6WDWLRQ 3URSHUW\ 9DOXH
>@ $GGUHVV (:
>@ >@.XU]VFKOXVVQDFK0
>@ >@8HEHUWHPSHUDWXU
>@ >@0DVVHIHKOHU
>@ >@.XU]VFKOXVVQDFK/
>@ >@*HEHUYHUVRUJXQJIHKOW
&KDQQHO >@([WHUQH/DVWVSDQQXQJIHKOW
&KDQQHO >@*OHLFKWDNWIHKOHU
>@ >@5HIHUHQ]NDQDOIHKOHU
>@ >@3UR]HVVDODUP$QDORJZHUWXHEHUVFKULWWHQ
>@ >@3UR]HVVDODUP$QDORJZHUWXQWHUVFKULWWHQ
6WDWLRQ
6WDWLRQ 3URSHUW\ 9DOXH
>@ $GGUHVV (:
>@ >@.XU]VFKOXVVQDFK0
>@ >@8HEHUWHPSHUDWXU
>@ >@0DVVHIHKOHU
>@ >@.XU]VFKOXVVQDFK/
>@ >@*HEHUYHUVRUJXQJIHKOW
&KDQQHO >@([WHUQH/DVWVSDQQXQJIHKOW
&KDQQHO >@*OHLFKWDNWIHKOHU
>@ >@5HIHUHQ]NDQDOIHKOHU
>@ >@3UR]HVVDODUP$QDORJZHUWXHEHUVFKULWWHQ
>@ >@3UR]HVVDODUP$QDORJZHUWXQWHUVFKULWWHQ
6HW,QWHUUXSW
3URFHVVYDOXH ,1 ,QWHUUXSW 6WDWLRQ>@>@>@B&KDQQHOB,QWHUUXSW
)DOVH ,1
)DOVH ,1
)DOVH ,1
Hardware interrupts
SIMATIC PLCs use hardware interrupts to monitor binary or analog I/O signals: When an
analog value is exceeded or undershot or when a binary value is set or reset, the cyclical
operation of the controller is interrupted to execute the reaction of the user program to this
interrupt. If and under which conditions a device or module triggers hardware interrupts is
defined in the STEP 7 project.
6HW,QWHUUXSW
)DOVH ,1 ,QWHUUXSW 6WDWLRQ>@>@>@B&KDQQHOB,QWHUUXSW
)DOVH ,1
)DOVH ,1
)DOVH ,1
)DOVH ,1
)DOVH ,1
)DOVH ,1
)DOVH ,1
3URFHVVYDOXH ,1
,1
See also
SetInterrupt (Page 549)
Introduction
For example, to simulate the failure of a line, device or module during a simulation, disable the
line, device or module in the coupling properties. In this way you can test, for example, the
reaction of the controller to failure and return of a line, device or module.
Deactivation works while simulation is running and during configuration.
Requirement
● Coupling of the type "SIMIT Unit" has been created.
● Station is open in the coupling editor.
● Station is configured.
Procedure
To disable a line, a device or a module, proceed as follows:
1. To disable a line:
– Select the line in the properties.
– Select the option "Line failure".
2. To disable a device:
– Select the device in the properties.
– Select the option "Slave failure".
3. To disable a module:
– Select the module in the properties.
– Select the option "Pull module".
Result
The line, device or module has been disabled.
See also
Configuring the station (Page 90)
Requirement
● Master system is connected to simulation.
● SIMIT Unit is connected to the PC on which SIMIT is installed.
● Station is configured.
Procedure
Note
Communication between the master system and controller is briefly interrupted during loading.
Result
The configuration is loaded to the SIMIT Unit. You can launch simulation for this station once
loading is complete.
See also
Configuring the station (Page 90)
Properties of a station
● Time slice
Here you set the cycle at which the coupling exchanges data. The assignment of absolute
cycle times to the 8 available time slices is valid for the entire project. The default is time slice
2, which corresponds to a cycle of 100 ms.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
● Mnemonics
Specifies whether the German ("E/A") or English ("I/Q") term for the absolute addresses is
used.
Note
Define the mnemonics immediately after import. If you subsequently change the
mnemonics, signals already interconnected in a chart can no longer be assigned to the
original address.
● H system
Shows that the system is an H system.
● F system
Shows that the system is an F system.
● Load project permanent
Specifies that the simulation project is also saved in the SIMIT Unit. You can continue the
simulation when the SIMIT Unit is restarted without having to load the simulation project to
the SIMIT Unit once again.
To delete the simulation project from the SIMIT Unit, disable the option and load the
configuration to the SIMIT Unit.
● Baud rate
Shows the transmission speed.
See also
Configuring the station (Page 90)
<HARDWARE>
<COMMENT/>
<NAME>SimbaPNIO_2[0]</NAME> Name of the simulation box, name is freely assignable, the
number in the square brackets at the end indicates the
channel of the box and must be present.
<HWTYPE>PNIO</HWTYPE> Type of simulation box. For PROFINET "PNIO"
<IOSUBSYSTEM>100</IOSUBSYSTEM> PROFINET system ID
<FIRSTDEVICE>6</FIRSTDEVICE> Topology information, the device that is directly behind the
controller and is thus simulated at the external interface of
the simulation box.
<FIRSTPORT>1</FIRSTPORT> The corresponding port for this.
<SUBSLOT>
<NAME>Port 1</NAME> Subslot for a port of the PNIO interface
<INDEX>32769</INDEX>
<TYPE>0000C000</TYPE>
<INLEN>0</INLEN>
<OUTLEN>0</OUTLEN>
<IOPS_Length>1</IOPS_Length>
<IOCS_Length>1</IOCS_Length>
</SUBSLOT>
<SUBSLOT>
<NAME>Port 2</NAME>
<INDEX>32770</INDEX>
<TYPE>0000C000</TYPE>
<INLEN>0</INLEN>
<OUTLEN>0</OUTLEN>
<IOPS_Length>1</IOPS_Length>
<IOCS_Length>1</IOCS_Length>
</SUBSLOT>
</PNIOSLOT>
<PNIOSLOT> Slot example for an input module
<NAME>SM 321 DI16xDC24V</NAME>
<ORDERNUMBER>6ES7 321-1BH50-0AA0</
ORDERNUMBER>
<INDEX>1</INDEX>
<TYPE>00009FC2</TYPE>
<API>0</API>
<CHILDTYPE>SUBSLOT</CHILDTYPE>
<SUBSLOT>
<TYPE>00000000</TYPE>
<INDEX>1</INDEX>
<NAME>14</NAME>
<INLEN>2</INLEN>
<OUTLEN>0</OUTLEN>
<IOPS_Length>1</IOPS_Length>
<IOCS_Length>1</IOCS_Length>
<LOGIN>6</LOGIN> Logical input address, must be unique AS-wide. Data is
exchanged from the interface via this address.
<CHILDTYPE>CHANNEL</CHILDTYPE>
</SUBSLOT>
</PNIOSLOT>
... Additional allocated slots
<PNIOSLOT>
<NAME>FDO10xDC24V/2A</NAME>
<INDEX>4</INDEX>
<TYPE>000008C1</TYPE>
<API>0</API>
<CHILDTYPE>SUBSLOT</CHILDTYPE>
<SUBSLOT>
<TYPE>00000000</TYPE>
<INDEX>1</INDEX>
<INLEN>6</INLEN>
OUTLEN>6</OUTLEN>
<IOPS_Length>1</IOPS_Length>
<IOCS_Length>1</IOCS_Length>
<LOGIN>18</LOGIN>
<LOGOUT>18</LOGOUT> Logical output address, must be unique AS-wide. Data is
exchanged from the interface via this address.
</SUBSLOT>
</PNIOSLOT>
</PNIODEV>
... Additional PNIO devices
<PNIODEV>
...
</PNIODEV>
</HARDWARE>
To check your XML file, copy the following text block from the second line into your XML file and
then load the entire file into a DTD Validator.
If you do not want to copy the text every time, copy the text block into a text file (for example,
"SIMXMLImport.dtd"), and install only a link to this text file for the validation in your XML files
in the second line.
<!DOCTYPE HARDWARE SYSTEM "SIMITXMLImport.dtd">
The first and last line of the text block must be omitted for use in an external DTD file.
XML validators on the Internet are, for example:
● https://www.xmlvalidation.com (https://www.xmlvalidation.com)
● https://www.w3schools.com/xml/xml_validator.asp (https://www.w3schools.com/xml/
xml_validator.asp)
However, they only work if the DTD is directly integrated into the XML file.
The "XMLNotepad2007" from Microsoft is suitable for offline XML validation.
2.6.1.1 Introduction
Function
The virtual controller simulates the response of a SIMATIC controller of the type S7-300 or
S7-400. The virtual controller is loaded with the original PLC user program. The field device
level and its connection over distributed bus systems are ignored. Instead, process simulation
is connected directly over the process image input and output.
You can use up to 32 virtual controllers in the simulation project, and can distribute them across
multiple PCs.
Virtual controllers can communicate with each other; connections to external partners and the
operator control and monitoring system are also possible. Only IP-based connections in
address space IPv4 are supported, however.
The figure below shows which automation level components are represented as virtual
controllers:
26VHUYHU
$XWRPDWLRQOHYHO
'LVWULEXWHG,2
352),1(7 352),%86'3
In SIMIT, all virtual controllers in a simulation project are shown and configured as separate
couplings in the project navigation under "Couplings > Virtual controllers". Data exchange
between SIMIT and the virtual controller is over these couplings.
NOTICE
Important information:
● Automation programs can be run on MS Windows with the virtual controller. As MS
Windows is not a real-time operating system, the following limitations apply:
– System availability
– Accuracy of simulation
You also cannot connect real I/O or bus systems.
● While the functions of the virtual controller have been tested for its intended use (testing
and training systems), we cannot guarantee that the system will always demonstrate the
exact time response. The functions provided cannot cover the complete functional scope
of a real controller in all situations.
The system is therefore not intended for the control of real plants.
The results obtained for virtual commissioning must be checked and evaluated by the user.
To protect the confidentiality of your data, use the virtual controller only as part of a holistic
Industrial Security concept that is state-of-the-art. Third-party products you are using should
also be considered.
You can find additional information on the Internet (http://www.siemens.com/
industrialsecurity).
7&3,3
Note
Supported STEP 7 version
The virtual controller coupling is supported up to and including STEP 7 V5.5.
Note
Use of CFC charts on an S7-410 simulated in the virtual controller
If you are simulating an S7-410 with the virtual controller, note the following when using CFC
charts:
Starting with CFC V8.2 Update 3, you can download a user program without any limitations. If
you are using an older version of CFC, follow the stops below on each PC configured as a
virtual controller:
1. Change to the following directory in Windows:
"Programs (x86)\Siemens\Automation\SIMIT\SIMIT VC\data\CPU"
2. Rename the following files:
– "6ES7 410 5HN08-0AB0" → "6ES7 410 5HN08-0AB0_CPU410"
– "6ES7 410 5HX08-0AB0" → "6ES7 410 5HX08-0AB0_CPU410"
3. Rename the following files:
– "6ES7 410 5HN08-0AB0_LEGACY" → "6ES7 410 5HN08-0AB0"
– "6ES7 410 5HX08-0AB0_LEGACY" → "6ES7 410 5HX08-0AB0"
As a result of this action, the virtual controller will signal back as S7-417. You can download the
project with CFC charts from PCS 7 to the PLC. If you update your CFC installation to the latest
version, you must undo this renaming.
Note
Delta download
With each delta download, SIMIT saves a time stamp in the controller. Based on the time
stamp, a decision is made as to whether the program is identical in the controller ("online") and
in SIMIT ("offline"). The virtual controller does not support saving this time stamp across a
restart of the simulation but stores the program correctly. SIMIT will therefore signal an
inconsistent status of the program when going online after a delta download and restart of the
simulation. You can avoid this message with a complete download.
Note
BlockPrivacy
The virtual controller cannot execute blocks that are protected with "BlockPrivacy".
If your project contains blocks that are protected this way, these are replaced by a NOP (No
Operation) in the virtual controller.
NOTICE
Adding and changing IP addresses
Changing an IP address can lead to communication problems in the network. For example, it
may no longer be possible to access a PC.
Never change IP addresses without consulting your IT administrator.
You can find additional information in section TCP/IP addressing and subnets (https://
support.microsoft.com/en-us/kb/164015).
See also
Configuring virtual controllers (Page 123)
2.6.1.3 Functions
The virtual controllers support the following basic controller functions, irrespective of the
specific type:
● Downloading the hardware configuration and application software to the virtual memory of
the virtual controllers
● Interpretation of MC7 code
● Provision of data areas, arithmetic unit, batteries and results of logic operations, counters,
timers, memory areas for process images, etc.
● OB management and scheduling
● Communication functions
● A selection of system functions (SFB/SFC) insofar as this is possible and useful in
virtualization.
Introduction
The virtual controller supports IP-based communication over Ethernet / PROFINET and the
following protocols:
'3 3$
$SSOLFDWLRQ/D\HU )06
63URWRFRO
3UHVHQWDWLRQ/D\HU
63URWRFRO
6HVVLRQ/D\HU
5)&
7UDQVSRUW/D\HU 8'3 ,62
7&3
1HWZRUN/D\HU ,3
'DWD/LQN/D\HU )'/
,(&
,QG(WKHUQHW
03, 352),%86
3K\VLFDO/D\HU
Supported:
● S7
● S7H
● TCP
● UDP
● RFC 1006
Note
Please note the restrictions that can result when using substitute functions in virtual controllers.
① The local IP addresses cannot be read out (system-related). You may need to correct these
addresses manually in the connection configurations.
② The IP addresses of the connection partner can be read out.
③ Result after import: Connection is correctly assigned.
Assumption: All connections to external partners are based on the lowest IP address.
④ Result after import: Connection is not correctly implemented.
On the basis of the assumption in ③, SIMIT enters "192.168.0.1" as the local address upon
import.
See also
Configuring virtual controllers (Page 127)
Supported system functions (Page 113)
Supported S7 blocks (Page 115)
Supported services (Page 116)
Only the standard functionalities, for example those of an S7-417-5H, are supported. For
extensions and additional functions of an AS 410-5H, virtual controllers map the functionality of
an S7-400 CPU 417-5H.
Note
● The use of SFCs is limited because, for example, the I/O are not simulated.
● Before using virtual controllers, verify that the SFBs and SFCs required by your automation
system are supported. You can check the reference data of the blocks in SIMATIC
Manager, for example. You can find additional information on the reference data in the
STEP 7 help.
● The substitute functions provide useful feedback on standard operation of the hardware
without faults, provided this is possible with the level of implementation and information from
the SIMATIC project. Only very limited information on response in the event of a fault is
possible, and must be checked by the user independently.
● User blocks and library components (FB, FC) can potentially access system functions that
are not supported by the virtual controller. In this case, the entire block is ignored
(NoOperation).
● If the automation program expects signals from these system functions, you can make the
corresponding (instance) DB in SIMIT addressable and write the expected information for
SIMIT straight to the corresponding DB.
● The virtual controller supports the "S7 F Systems Lib V1_3" library and "Safety Matrix" in
failsafe operation. Error states cannot be mapped. F communication is only possible
between two virtual controllers in a SIMIT instance.
● "Distributed Safety" is not supported.
Introduction
Real controllers provide comprehensive services that allow access to the controller.
SIMIT VC supports the following communication services, which are required for
communication between virtual controllers and PCS 7 OS/WinCC servers or PCS 7 OS/WinCC
clients. These services provide answers to the following queries that can be sent over the
S7_DOS interface of PCS 7 OS/WinCC.
Note
The virtual controller does not answer other queries. Systems that rely on other services cannot
therefore communicate correctly with the controllers emulated. These include, for example:
● BRAUMAT Classic
● AS based Batch
Supported S7 services
● SPS7
– Set up application relationship
– Cancel application relationship
– Status_Virtuelles_Gerät
– DataExchange2 Cancel
● Operator control and monitoring
– Reading (variable / segmented)
– Writing (variable / segmented)
– Zyklisches_Lesen_Einrichten
– Änderungsgesteuertes_Zyklisches_Lesen_Einrichten
– Auftrag_starten
– Auftrag_stoppen
– Auftrag_löschen
– Ändern_Zyklisches_Lesen with delta evaluation
– Ändern_Zyklisches_Lesen without delta evaluation
● Diagnostics
– An_Abmelden
– Acknowledgment
– Quittierung_an_alle
– Sperren_Meldungen
– Freigeben_Meldungen
– Sperren_an_alle
– Freigeben_an_alle
– Update
– Update_anfordern_an_alle
– SZL_Lesen (forward to SoftPLC online interface)
Note
Forcing is not supported.
The sequential control system of SIMIT does not interrupt OBs already running. They are
classified according to their priority in the basic cycle of SIMIT .
The following figure has a basic cycle time of 100 ms:
total cycle increases and the next basic cycle is therefore delayed. In the subsequent cycle,
SIMIT internally corrects all times (as shown in the figure above), changing them from "400+x"
back to "400", and continues calculations on that basis even if the real time is already at
"400+x". This keeps the virtual simulation time consistent.
Note
SIMIT distinguishes between timer times and the system time, which is used, for example, to
send messages. The system time is regularly synchronized with the system time of the SIMIT
computer, irrespective of the progress of the timer times.
See also
Access to a data record or memory area (Page 188)
Note
You can enter substitute mechanisms on the "DB" tab in the coupling editor of the virtual
controller coupling. You can find additional information in section: Properties of the Virtual
Controller coupling (Page 135).
See also
Supported system functions (Page 113)
Creating snapshots
The virtual controller can save snapshots while simulation is running. The snapshots are saved
in the SIMIT project directory and are therefore part of a SIMIT project archive. Snapshots
remain unchanged even if changes are made to the SIMIT project.
The following information is not included in snapshots:
● The states of connected systems
● Communication between virtual controllers
● Communication between virtual controllers and connected systems
Note
Snapshots are assigned to a virtual controller on the basis of its name.
If you change the name of a virtual controller in the project navigation after a snapshot is
created, the snapshot can no longer be linked to that virtual controller. Do not rename the virtual
controller in the project tree after creating a snapshot.
Note
Snapshots after changes to simulation
Snapshots save the states of the model and of individual virtual controllers.
● Please note that data in the snapshot is mapped by name (signal names, DB numbers, etc.).
There is therefore no guarantee that a snapshot will lead to a useful simulation or virtual
controller state after changes to the simulation (model or automation program). It is
irrelevant in this case whether the change was caused by the user or the user program (for
example, by using system functions such as CREAT_DB).
● Please note in particular that any existing snapshots may no longer be correctly assigned
if a virtual controller is renamed.
Requirement
● The IP addresses of the stations on the plant bus and terminal bus are known.
● The IP addresses in the company/simulation network are known.
● All IP addresses are unique.
Action overview
The figure below shows the procedure for creating a Virtual Controller coupling:
6,0,76)
6,0,79&
352),1(77&3 352),%86'3
See also
Creating a Virtual Controller (Page 125)
Creating a HWCN export file (Page 62)
Importing a STEP 7/PCS 7 project (Page 126)
Configuring an additional PC (Page 132)
Properties of the Virtual Controller coupling (Page 135)
Requirements for a simulation network (Page 109)
Introduction
Create a virtual controller coupling in a SIMIT project. Under a virtual controller coupling, you
can import stations from one or more STEP 7/PCS 7 projects.
Note
Supported STEP 7 version
The virtual controller coupling is supported up to and including STEP 7 V5.5.
Requirement
● Project is open in SIMIT.
● No virtual controller coupling has been saved in the project.
● There is a STEP 7/PCS 7 project or HWCNExport file.
Procedure
Proceed as follows to create a virtual controller coupling:
1. Select the "New coupling" command from the "Couplings" shortcut menu in the project
navigation.
The "Selection" dialog box opens.
2. Select the coupling type "Virtual controller".
The "Virtual controller import" dialog box opens.
3. Configure station import from a STEP 7/PCS 7 project or the HWCNExport file.
Note
After creating a virtual controller, the complete station must be downloaded to the running
virtual controller because the virtual controller reads information from the system data block
during runtime.
When you make changes to the controller configuration, the complete station must once again
be downloaded.
Result
You can find the result after the import of a STEP 7/PCS 7 project under Importing a STEP 7/
PCS 7 project (Page 126).
If you complete the "Virtual controller" type coupling without importing a STEP 7/PCS 7 project,
only the "Virtual controller" folder is created under "Couplings" in the project navigation.
See also
"Virtual controller import" dialog box (Page 929)
"Selection" dialog box (Page 943)
Configuring virtual controllers (Page 123)
Introduction
To allow you to create a simulation with a virtual controller coupling, import the stations from a
STEP 7/PCS 7 project. The following information from the STEP 7/PCS 7 project is applied:
● CPU
● Central I/O modules
● Distributed I/O modules
● Connections
You can run the import again at any time, for example to update configuration data or to add
new stations. Identical stations are identified using the following criteria:
● Project name
● Station name
● Storage location in the STEP 7/PCS 7 project
As an option, you can also select the stations to be imported when you configure import.
Note
Supported STEP 7 version
The virtual controller coupling is supported up to and including STEP 7 V5.5.
Requirement
● A "Virtual Controller" type coupling has been created.
● SIMATIC Manager is installed or there is a HWCNExport file.
Procedure
Proceed as follows to import a STEP 7/PCS 7 project:
1. Select the "Import" command in the "Couplings > Virtual controller" shortcut menu in the
project navigation.
The "Virtual controller import" dialog box opens.
2. Select the required STEP 7/PCS 7 project or the HWCNExport file.
3. Select the mode for importing the symbols.
4. Select the required stations.
5. Click "Import".
Result
A Virtual Controller is created in the project navigation under "Couplings > Virtual controller" for
each station from the STEP 7/PCS 7 project. The Virtual Controllers imported are assigned to
the emulation PC "My Computer" in the "Distribution" editor after the first import.
See also
Creating a HWCN export file (Page 62)
"Virtual controller import" dialog box (Page 929)
Configuring virtual controllers (Page 123)
Editing the signals of a coupling (Page 182)
Requirement
● The STEP 7/PCS 7 project has been imported.
● A Virtual Controller coupling has been created.
Procedure
Proceed as follows to configure a Virtual Controller:
1. Double-click on the required virtual controller under "Couplings > Virtual Controller" in the
project navigation.
2. Configure the virtual controller in the property view:
– Select the "Time slice".
– If necessary, enter the serial number of the "CPU" and/or memory card.
– Adjust the cycle time of the OBs if necessary.
3. Import selected address ranges of one or more data blocks as required.
See also
Basics of Virtual Controller communication (Page 111)
Properties of the Virtual Controller coupling (Page 135)
"Importing signal properties" dialog box (Page 932)
Distribution editor
In the distribution editor, you distribute the virtual controllers between additional PCs. This
spreads the load for simulation across multiple PCs.
Double-click to open the distribution editor under "Couplings > Virtual controller" in the project
navigation.
The figure below shows the structure of the distribution editor:
① Menu bar
② Represents the PC on which the SIMIT project is open.
③ Virtual controllers that you have imported from a STEP 7/PCS 7 project. These virtual controllers are by default
assigned to the PC "My Computer".
④ Additional PC (optional)
The PC must be located in the same network as the PC "My Computer". You distribute the available virtual controllers
among the PCs with drag & drop.
⑤ Property view
In the properties window, you configure the properties of the selected PC or virtual controller. Conflicts such as
duplicate IP addresses and inaccessible PCs are also displayed under "Diagnostics".
Menu bar
You can execute the following functions in the menu bar of the distribution editor:
● "Save"
Saves the configuration.
● "New computer"
Adds a new PC. The PC must be located in the same network as the PC "My Computer".
Properties of "Distribution"
Double-click on "Distribution" in the project tree to open the "Distribution" properties.
It specifies for each protocol which addresses are used for the identification of the
communication partners. You can find additional information in section Basics of Virtual
Controller communication (Page 111).
● "Computer name"
Specifies the computer name of the PC on which a virtual controller is to be hosted.
All PCs including "My PC" must be in the same subnet. As long as the PC "My PC" is set on
the LoopBack adapter (127.0.0.1), no other PCs are shown.
● "Computer address"
Shows the IP address of the PC by which it is currently identified in the network.
● "Station addresses"
Shows the IP addresses of the virtual controllers that are assigned to this PC.
Enter these IP addresses in the network settings of this PC. If an IP address is not to be used
in the simulation, disable that IP address in the virtual controller settings.
● "Name"
Shows the name of the virtual controller.
The name is taken from the STEP 7/PCS 7 project.
● "Active IP addresses"
Shows the configured IP addresses of the virtual controller.
Lists the IP addresses of the PLC and CPs plugged into the station. Enable an IP address
to use it in the simulation. If you disable an IP address, a connection used by that IP address
will not be simulated. Connections between virtual controllers are always simulated
irrespective of this.
● "Excluded blocks"
Specifies the STEP 7 blocks that are not to be included in the simulation.
Separate multiple blocks with commas. Invalid entries are deleted automatically when you
exit the text box.
● "S7 Clock"
Specifies the time format for the internal clock supplied to the virtual controller by the PC.
– Local time
– Universal Time Coordinated
● "Project name (SIMATIC)"
Shows the name of the STEP 7/PCS 7 project.
● "Station name (SIMATIC)"
Shows the station name.
● "Storage path (SIMATIC)"
Shows the storage path of the STEP 7/PCS 7 project.
● "Instance number (virtual controller)"
Shows the instance number of the virtual controller.
The instance number is assigned automatically by SIMIT.
Diagnostics
The virtual controllers are checked when a project is imported.
Errors such as incorrect IP addresses are highlighted in color and reported in plain text in the
diagnostics view.
The displays in the diagnostics view disappear automatically when the errors are dealt with. If
they do not, click "Refresh" in the distribution editor.
See also
Configuring an additional PC (Page 132)
Introduction
For complex simulations with multiple virtual controllers, one single PC often does not have
sufficient capacity. You can distribute the load evenly by connecting additional PCs to the
simulation network. You then assign each additional PC one or more virtual controllers in the
SIMIT project.
Note
Configuration limits
One SIMIT project can have a maximum of 32 virtual controllers.
One PC can simulate multiple virtual controllers. As a rule of thumb: A CPU core can run ca. two
virtual controllers. The actual CPU power required depends on the complexity of the simulation.
Requirement
● The PC is accessible in the network.
● Firewall is set up (Page 52).
● "SIMIT VC" is installed on the PC.
● A coupling of the type "Virtual controller" has been created.
● Virtual controllers from STEP 7/PCS 7 project are imported.
● The "Distribution" editor is open.
● Simulation has stopped.
Procedure
Proceed as follows to configure an additional PC:
1. Change the IP address of the PC "My Computer" from "127.0.0.1" to the IP address at which
the PC is accessible in the network.
2. Create an additional PC:
– Click on "New computer" in the "Distribution" editor.
– Select the name of the PC.
3. Drag the desired virtual controller to the PC with drag & drop.
4. In the property view of the virtual controller, go to "Properties > Active addresses" and select
the IP addresses that are used in the simulation.
5. Add these IP addresses in the network settings of the PC.
6. In the "Distribution" editor, click on "Save and distribute".
Result
The configuration is saved. The simulation project is now distributed across the PCs.
Conflicts such as duplicate IP addresses and inaccessible PCs are displayed in the property
view under "Diagnostics".
See also
Requirements for a simulation network (Page 109)
Configuring virtual controllers (Page 123)
Distribution editor (Virtual Controller) (Page 128)
If you click on a virtual controller symbol, the following display window opens.
See also
"Virtual controller import" dialog box (Page 929)
Properties of the Virtual Controller coupling (Page 135)
Mapping of SIMATIC data types in SIMIT (Page 187)
"I/O" tab
Here the inputs and outputs of the coupling are listed. You can find additional information on
this in section: Coupling editor (Page 61).
You can find additional information on importing signal properties in "Importing signal
properties" dialog box (Page 932).
You can find additional information on exporting signal properties in "Exporting signal
properties" dialog box (Page 935).
"DB" tab
If you need values of PLC data blocks for the simulation, you can enter the addresses or import
them using the "STL import" button. You can find additional information on this in section:
Importing DB data from STL sources (Page 138).
Note
The addresses are not validated.
● "Mnemonics"
Specifies whether the German ("E/A") or English ("I/Q") term for the absolute addresses is
used.
Note
Define the mnemonics immediately after import. If you subsequently change the
mnemonics, signals already interconnected in a chart can no longer be assigned to the
original address.
Properties of a module
● "Module name"
Shows the module name.
● "MLFB"
Shows the Siemens order number.
● "Module slot"
Shows the module slot.
See also
Configuring virtual controllers (Page 123)
Introduction
The following information is transferred to SIMIT when you import from an STL data source:
● Comment
● When you import inputs: default input assignment
The following data types are applied:
● STRING (implemented as BYTE ARRAY)
● ARRAY
● STRUCT
● UDT
● BOOL
● BYTE
● WORD
● DWORD
● INT
● DINT
● REAL
● CHAR
Note
Always select all utilized STL data sources when you generate the STL sources in STEP 7. If
a data block includes a UDT, for example, also add this structure definition when you generate
the STL source.
The following data types are included in addressing but not applied:
● S5TIME
● TIME
● DATE
● TIME_OF_DAY
● DATE_AND_TIME
Requirement
● Virtual controller is open.
● The "DB" tab is enabled.
● STL source with data block information exported from STEP 7 is available.
Procedure
Proceed as follows to import DB data from STL sources:
1. Click "STL import".
The "STL import" dialog box opens.
2. Select the STL source.
3. Enter the data block number.
4. Select the direction.
5. Enter the start and end bytes.
Note
Any existing signals in the specified memory area of "From byte" and "Up to byte" are
overwritten.
6. Click "Import".
Result
The specified address range of the data block is imported.
See also
"STL import" dialog box (Page 931)
Properties of the Virtual Controller coupling (Page 135)
Operating principle
SIMIT uses the PLCSIM Advanced coupling to communicate with PLCSIM Advanced over a
software interface of PLCSIM Advanced. SIMIT uses the PLCSIM Advanced coupling to
cyclically exchange data of the I/O area of the configured S7-1500 stations. SIMIT supports up
to 16 stations per PC.
Note
You may have to observe additional restrictions and notes in the PLCSIM Advanced
documentation.
See also
Creating a coupling of the "PLCSIM Advanced" type (Page 140)
Introduction
You can create a coupling of the "PLCSIM Advanced" type in a SIMIT project. You create
"stations" under the coupling to which you import the hardware configuration of a station from
STEP 7.
Requirement
● Project is open in SIMIT.
● TIA Portal Openness is installed on the SIMIT PC.
● STEP V14 SP1 is installed on the SIMIT PC or an HWCNExport file is available.
Procedure
Follow these steps to create a coupling of the "PLCSIM Advanced" type:
1. Add a new coupling under "Couplings" in the project tree.
The "Selection" dialog box opens.
2. Select the coupling type "PLCSIM Advanced".
The "PLCSIM Advanced Import" dialog box opens.
3. Configure the station import from a STEP 7 project or from the HWCNExport file.
Result
You can find the result after import of a STEP 7 project in Importing hardware configuration to
station (Page 141).
If you complete the coupling of the type "PLCSIM Advanced" without importing a STEP 7
project, only the "PLCSIM Advanced" folder is created in the project tree under couplings.
See also
"PLCSIM Advanced import" dialog box (Page 928)
Creating a HWCN export file (Page 62)
Introduction
You import the hardware configuration directly from STEP 7. Import the hardware configuration
to the station in SIMIT again if you have changed the hardware configuration in STEP 7.
When importing the hardware configuration from the TIA Portal, the following structures are
evaluated in addition to the simple data types and imported as WORD:
● PD_ZSW1
● PD_ZSW2
● PD_Gx_ZSW
● PD_STW1
● PD_STW2
● PD_Gx_STW
● PD_MELDW
Requirement
● A "PLCSIM Advanced" type coupling has been created.
● STEP 7 V14 SP1 is installed on the SIMIT PC.
● Hardware configuration is compiled and loaded in STEP 7.
Procedure
Follow these steps to import the hardware configuration to a station:
1. Select the "Import" command from the "Couplings > PLCSIM Advanced" shortcut menu in
the project tree.
The "PLCSIM Advanced import" dialog box will open.
2. Select the source from which you want to import the hardware configuration.
3. Select the mode for importing the symbols.
4. Select the required stations.
5. Click "Import".
Result
A station is created for each station from the STEP 7 project in the project tree under "Couplings
> PLCSIM Advanced". During the initial import the imported stations are assigned to the
emulation PC "Own computer" in the "Distribution" editor.
See also
"PLCSIM Advanced import" dialog box (Page 928)
Creating a coupling of the "PLCSIM Advanced" type (Page 140)
Creating a HWCN export file (Page 62)
Editing the signals of a coupling (Page 182)
Requirement
● Station has been created.
● Hardware configuration has been imported.
Procedure
Follow these steps to configure a station of a PLCSIM Advanced coupling:
1. Set the "time slice" using the shortcut menu of the PLCSIM Advanced coupling.
2. Open the Distribution Editor of the PLCSIM Advanced coupling.
3. Configure each station in the properties window:
– Enter a name if required.
– Specify the communication path.
Result
The station is configured. Import (Page 197) signal properties to add input and output signals.
You can edit signal properties.
You can find additional information on editing and exporting signals in:
● Editing the signals of a coupling (Page 182)
● Exporting signal properties (Page 199)
See also
Distribution editor (PLCSIM Advanced) (Page 143)
Importing hardware configuration to station (Page 141)
Distribution editor
You configure the stations of a PLCSIM Advancedcoupling in the distribution editor.
Double-click the distribution editor to open it in the project tree under "Couplings > PLCSIM
Advanced".
Menu bar
You can execute the following functions in the menu bar of the distribution editor:
● "Save"
Saves the configuration.
Properties of a station
● Name
Specifies the station name in the SIMIT project. Change the name in the project navigation
using the station shortcut menu.
● "Project name (SIMATIC)"
Shows the name of the STEP 7 project.
● "Station name (SIMATIC)"
Shows the station name.
● "Storage path (SIMATIC)"
Shows the storage path of the STEP 7/PCS 7 project.
● Instance number (VC)
Shows the instance number.
The instance number is assigned automatically by SIMIT.
See also
Configuring a PLCSIM Advanced coupling station (Page 142)
Note
To use the PLCSIM coupling, you also need the PLCSIM software version 5.4 SP5 or higher.
This software is not included in the SIMIT product package.
PLCSIM is a program that can be used independently of SIMIT and can be loaded from
SIMATIC Manager with a STEP 7 program. PLCSIM will then simulate a SIMATIC controller.
In order to simulate the controller behavior as realistically as possible, we recommend that you
always load the STEP 7 program along with the system data blocks (SDBs) into PLCSIM.
Note
The hardware configuration is also determined through the system data. In the SIMIT coupling
with PLCSIM, data exchange is only possible for I/O signals that are defined by the configured
hardware.
● Time slice
The cycle in which the coupling exchanges data is set here. The assignment of absolute
cycle times to the 8 possible time slices applies to the entire project. Time slice 2, which
corresponds to a cycle of 100 ms, is preset.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
● PLCSIM number
You can create up to 8 PLCSIM couplings in a project to connect to the corresponding
instances of PLCSIM. Select the number of the PLCSIM instance with which the coupling is
to communicate here. The number can be found in the PLCSIM window header line.
If you set the PLCSIM number to "Not assigned", no connection with PLCSIM will be
established when the simulation is started and there will be no data exchange.
● Mnemonics
Here, you select whether the international (I/Q) or German (E/A) mnemonics are to be used
for the inputs and outputs.
Additional functions
Introduction
OPC is a widely used communication standard in the automation sector, and is maintained and
supported by the OPC Foundation (www.opcfoundation.org). The OPC protocol is used for
device-independent data exchange between programs with OPC capability.
23&&OLHQW 23&&OLHQW
7&3,3
23&6HUYHU
)LHOGGHYLFHV
In the OPC Classic Architecture, an OPC server is connected to a subordinate device layer
whose signals are made available via the local network to one or more OPC clients.
Note
To protect the confidentiality of your data, use the OPC coupling only as part of a holistic, state-
of-the-art industrial security concept. This should take into account products from other
manufacturers that are being used.
You can find additional information on the Internet (http://www.siemens.com/industrialsecurity).
Browsing functionality
SIMIT supports the browsing functionality which allows you to apply the data provided by an
OPC server automatically to the signal table.
See also
Principle of operation of the SIMIT OPC DA server (Page 151)
Principle of operation of the OPC DA client coupling (Page 158)
Cycle multiplier
The cycle multiplier is an integer, "n", which only updates values in every nth cycle. By
specifying a cycle multiplier, you the reduce the load on the communication connection
between OPC server and OPC client. You can configure the cycle multiplier separately for each
signal provided by the OPC server.
● Signal changes frequently: Small cycle multiplier
● Signal changes slowly: Large cycle multiplier
Example: For an OPC client coupling, a cycle time of 250 ms is set with the time slice. A signal
is configured with a cycle multiplier of "4". The signal is therefore only updated every
250 ms × 4 = 1000 ms.
Quality code
Signals transferred between OPC server and OPC client by default also return a "quality code"
that indicates the quality of the signal. For each output signal of an OPC client coupling, SIMIT
by default creates an integer "quality signal" containing the quality code. The signal name is
structured as follows: <Name of output signal>.<quality>
You can use the quality signal in charts, like all other signals. While a simulation is running, the
"quality code" is displayed in the properties of each quality signal.
Signals transferred from the SIMIT OPC client to an OPC server output the following quality
code:
● "Good, non-specific". This corresponds to "0xC0" or "192".
There is no data loss in conversion for output signals of the coupling, as integer and analog
signals in SIMIT have the maximum data width (8 bytes).
Mapping of signals
The signals of the OPC server can be read or written or both. They are treated as inputs or
outputs in SIMIT depending on this read/write access.
OPC SIMIT
readable Output
writeable Input
readWriteable Input
Core statement
While simulation is running, the properties window of the OPC client coupling displays the
current status of the OPC server addressed. The status is also output with an output signal that
you define when you configure the coupling.
The table below shows the meaning of the possible status values:
Note
Which of these status values an OPC server provides depends on the OPC server
implementation.
See also
Properties of the OPC DA client coupling (Page 155)
Data transmission
The SIMIT OPC DA server checks regularly in the simulation model whether the values have
changed. The SIMIT OPC DA server supports synchronous and asynchronous data
transmission:
● Synchronous data transmission All values are cyclically transmitted.
● Asynchronous data transmission Only changed values are transmitted. The SIMIT OPC DA
server automatically groups values. Criteria for grouping are:
– Data type and multiplier, each for input and output values
All values in a group are generally transmitted in case a value has changed.
Status messages
The SIMIT OPC DA server outputs the following status that can be queried by an OPC DA
client:
SIMIT OPC
Binary BOOL
Integer I8 if the option "Use 64-bit integer" is selected, otherwise I4
Analog R8
See also
How the OPC coupling works (Page 147)
Requirements
● Project is open in SIMIT.
Procedure
Follow these steps to create a SIMIT OPC DA server coupling:
1. Select the "New coupling" command from the "Couplings" shortcut menu in the project
navigation.
2. Select the coupling type "OPC DA server".
3. Select a time slice with an update cycle of at least 100 ms.
4. If the OPC DA client and OPC DA server are installed on different PCs, please see the
"Notes on DCOM configuration (Page 156)".
Result
The SIMIT OPC DA server is configured. The following options are available for adding input
and output signals:
● Entering signals manually
● Importing the signal table (Page 197)
See also
Properties of the SIMIT OPC DA server coupling (Page 154)
Mapping of signals and data types of an OPC server (Page 150)
Introduction
The OPC DA client coupling only supports asynchronous data transmission from one OPC DA
server to another. An OPC DA server automatically groups values. All values in a group are
transmitted in case a value changes.
Requirements
● Project is open in SIMIT.
● ProgID of the OPC DA server is known.
● Host name of the PC on which the OPC DA server is installed is known.
● OPC DA server can be accessed in the network.
Procedure
Follow these steps to create an OPC DA client coupling:
1. Select the "New coupling" command from the "Couplings" shortcut menu in the project
navigation.
2. Select the coupling type "OPC DA client".
3. Configure the connection to the OPC DA server.
4. If the OPC DA client and OPC DA server are installed on different PCs, please see the
"Notes on DCOM configuration (Page 156)".
Result
The coupling with the OPC DA server is configured. The following options are available for
adding input and output signals:
● Reading signals from an OPC server (Page 211)
● Importing the signal table (Page 197)
● Entering signals manually
See also
Properties of the OPC DA client coupling (Page 155)
Editing the signals of a coupling (Page 182)
● Time slice
This is where you set the cycle in which the coupling exchanges data. The assignment of
absolute cycle times to the 8 possible time slices applies to the entire project. The default is
time slice 2, which corresponds to a cycle of 100 ms in the standard setting.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
The OPC server updates its data every 100 ms. Cycle times below this value should
therefore not be set.
● Server name
The SIMIT OPC server name is displayed for information only. It is set to "SIMIT OPC DA
Server". The server name or ProgID is needed to configure an OPC client for access to this
OPC server.
● ProgID
The ProgID of the SIMIT OPC server is displayed for information only. It is set to
"Simit.OpcDaServer.8". The ProgID or server name is needed to configure an OPC client
for access to this OPC server.
● Use 64-bit integers
Integer values in SIMIT have a data width of 64 bits (8 bytes). They are therefore also saved
in this format in the OPC server coupling.
Deselect this option if an OPC client connected to this OPC server cannot process integer
values with a data width of 8 bytes. SIMIT then transfers all integer values with a data width
of 32 bits (4 bytes) only. Note that this may lead to loss of data if a number cannot be
represented with 32 bits.
See also
"Importing signal properties" dialog box (Page 932)
"Exporting signal properties" dialog box (Page 935)
Configuring a SIMIT OPC DA server coupling (Page 153)
● Time slice
This is where you set the cycle in which the coupling exchanges data. The assignment of
absolute cycle times to the 8 possible time slices applies to the entire project. The default is
time slice 2, which corresponds to a cycle of 100 ms in the standard setting.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
● Host name
The name of the computer on which the OPC server is running. This is the OPC server with
which the coupling communicates. You can provide either the computer name or its IP
address. The default is the local computer (localhost).
● ProgID
Here, enter the ProgID of the OPC server with which the OPC client is to connect on the
computer specified under host name.
If the connection is local, i.e. "localhost" is entered under host name, the ProgIDs of the OPC
servers that are available locally will be available for selection. Select the OPC server with
which the coupling is to communicate.
If the ProgID is set to "Not assigned", no connection to an OPC server is established when
the simulation is started. The coupling signals are not updated cyclically.
● Status display
Specifies the name of the integer output signal that provides the status of the connected
OPC server while simulation is running. You can use this output signals to evaluate the
server status in your SIMIT project. One output signal is generated for each OPC DA client
coupling.
See also
"Importing signal properties" dialog box (Page 932)
"Exporting signal properties" dialog box (Page 935)
Status of OPC servers (Page 150)
Configuring an OPC DA client coupling (Page 153)
Note
All settings in the rights systems of a Windows PC depend greatly on the operating system
version and the programs already installed on your PC. We can therefore only give you a guide
and not precise instructions for the configuration of DCOM in your specific environment.
Note
Only change settings on your PC if you know exactly what they mean. Make sure that you do
no inadvertently leave your PC unprotected.
Firewall configuration
If you use a firewall, you will need to enable TCP port 135 for incoming queries for DCOM. You
must ensure that none of the OPC servers or OPC clients or the two programs "Microsoft
Management Console" and "OPCEnum" are blocked.
Assignment of rights
When an OPC connection is established over DCOM, a PC accesses the resources of or
launches specific processes on another PC. You will need specifically to allow this, as it
involves processes that could potentially put your PC at risk.
Both the access rights and start and activation rights need to be correctly set.
Recommendation: Set up a new user group with these advanced access rights. Assign the
users who use the OPC connection to this user group.
As well as making general COM security settings, you also need to set the rights of the OPC
server and the system utility program "OPCEnum.exe".
The program "dcomcnfg.exe" under Windows 7 is used for configuration.
Details of DCOM configuration can be found in "Using OPC via DCOM with Windows XP
Service Pack 2" from the OPC Foundation, available on the Internet at http://
www.opcfoundation.org.
See also
Configuring a SIMIT OPC DA server coupling (Page 153)
Configuring an OPC DA client coupling (Page 153)
Introduction
You can create up to 32 OPC UA client couplings in SIMIT. Each OPC UA client can contact an
OPC UA server and exchange data.
The OPC UA client coupling supports secure data transfer.
See also
Mapping of signals and data types of an OPC server (Page 150)
How the OPC coupling works (Page 147)
Certificates (Page 158)
2.9.6.2 Certificates
Introduction
For data exchange over OPC UA, certificates confirm the identity of the connection partner. The
certificates are automatically exchanged by the OPC UA client and OPC UA server when a
connection is first established. Before each subsequent connection, the system checks
whether the certificates are still valid.
Storage of certificates
The following directory structure is created in the "C:\ProgramData\Siemens\Automation\SIMIT
\8.0\PKI\" directory during SIMIT installation. Within this directory structure, members of the
"Administrators" group have full access.
● "issuers": Contains certificates required for verifying CA certificates.
Access rights:
– "Users" group: Read
● "own": Contains the "Application Instance Certificate" and the private key of the OPC UA
client, which is generated during installation. The OPC UA server reads this directory when
a connection is first established. The private key is only generated once and is not
overwritten when the software is updated.
Access rights:
– "Users" group: No access in the \private subdirectory
– "Users" group: Read in \certs subdirectory
● "trusted\certs": Contains certificates of OPC UA servers with which the OPC UA client can
exchange data.
Access rights:
– "Users" group: Read
● "rejected\certs": Contains rejected OPC UA server certificates.
Access rights:
– "Users" group: Write
See also
Configuring an OPC UA client coupling (Page 160)
Requirements
● Project is open in SIMIT.
● URL of the PC with installed OPC UA server is known.
● The OPC UA server can be accessed in the network.
● The OPC UA server support the authentication method "Anonymous".
● Access rights to the following directories are available:
– "C:\ProgramData\Siemens\Automation\SIMIT\8.0\PKI\own\private": Read
– "C:\ProgramData\Siemens\Automation\SIMIT\8.0\PKI\trusted\certs": Write
Procedure
Follow these steps to create an OPC UA coupling:
1. Select the "New coupling" command from the "Couplings" shortcut menu in the project
navigation.
2. Select the coupling type "OPC UA client".
3. Configure the connection to the OPC UA server.
4. If you configure secure data transfer:
– Copy the certificate sent by the OPC UA server from the "..\rejected\certs" folder to the
"..\trusted\certs" folder.
– On the OPC UA server, add the OPC UA client to the list of "trusted clients".
Result
The coupling with the OPC UA server is configured. The following options are available for
adding input and output signals:
● Reading signals from an OPC server (Page 211)
● Importing the signal table (Page 197)
● Entering signals manually
See also
Properties of the OPC UA client coupling (Page 161)
Mapping of signals and data types of an OPC server (Page 150)
Error messages upon connection to the OPC UA server (Page 161)
Certificates (Page 158)
Editing the signals of a coupling (Page 182)
● End point
Specifies the OPC UA server and transfer mode.
– Protocols supported: OPC UA binary protocol (communication profile "UA-TCP UA-SC
UA Binary")
– Security policies supported: Basic256Sha256, Basic256, Basic128Rsa15, None
– Security modes supported: None, Sign, Sign&Encrypt
● Name space URI
Specifies the scope of the signals provided by the selected OPC UA server. An OPC UA
server can provide multiple name spaces. To use signals from multiple name spaces, create
a separate OPC UA client coupling for each name space.
● Status display
Specifies the name of the integer output signal that provides the status of the connected
OPC server while simulation is running. You can use this output signals to evaluate the
server status in your SIMIT project. One output signal is generated for each OPC UA client
coupling.
See also
Configuring an OPC UA client coupling (Page 160)
Status of OPC servers (Page 150)
SIMIT uses the Shared Memory coupling, SHM coupling for short, to communicate with any
number of other applications over shared memory (SHM). This coupling is all-purpose and high-
performance.
Input signals are the signals that are written by SIMIT to the memory area and output signals
are the signals that are read by SIMIT from the memory area.
$SSOLFDWLRQ
,QSXWVLJQDOV
2XWSXWVLJQDOV
VKDUHGPHPRU\DUHD
VKDUHGPHPRU\
6,0,7
Note
Access to the shared memory area is not limited to a particular user. Each application that runs
on this PC has access to the shared memory area.
Note
Each application that is connected to SIMIT over an SHM coupling should minimize the time for
which it blocks the mutex so as not to block access to the shared memory area by SIMIT and
other applications for longer than necessary.
%\WH
6L]HRIWKHPHPRU\DUHD >%\WH@
Data area
$GGUHVV %\WH
0[
0%
0:
'DWDDUHD
0'
%\WH
6L]HRIWKHPHPRU\DUHD >%\WH@
Header area
6L]HRIWKHKHDGHUDUHD >%\WH@
If SIMIT creates the shared memory area, SIMIT can optionally add additional variables and a
list of signals to the header area. This information can then be used by applications to configure
their access to the data area.
%\WH
6L]HRIWKHPHPRU\DUHD >%\WH@
6L]HRIWKHKHDGHUDUHD >%\WH@
9HUVLRQ >%\WH@
6FDQQLQJF\FOHLQPV >%\WH@
Header area
&\FOHFRXQWHU >%\WH@
/HQJWKRIPXWH[QDPH >%\WH@
P
Signal list
The version identifies the memory structure. As the structure defined here has the version
identifier "0", you will always find a value of "0" entered here. If the structure of the memory area
is altered, the version is changed accordingly.
The predefined sampling time slice for the SHM coupling is entered in milliseconds (ms) as an
integer value.
In each cycle of the SHM coupling, the integer value of the cycle counter is incremented by 1.
The length of the mutex name, which means the number m of characters in the mutex name,
is stored in byte 16 of the header area. The mutex name is saved in the following header area
from byte 17.
The signal list created from byte 17+m onwards in the header provides information about the
signals in the data area. The following variables are specified for each signal:
● Length of the signal name, i.e. the number of characters in the signal name
● Signal name
● Address of the signal, i.e. the signal offset in the data area
● I/O identifier, the identifier that shows whether a signal is an input signal (0) or output signal
(1)
● Type identifier for the data type
The figure below shows the structure of the signal list in the header area:
%\WH
P /HQJWKRI6LJQDOQDPH >%\WH@
P
$GGUHVVRI6LJQDO >%\WH@
Signal list
PV ,2LGHQWLILHURI6LJQDO >%\WH@
PV 7\SHLGHQWLILHURI6LJQDO >%\WH@
PV
Signal2, etc.
(QGLGHQWLILHURIVLJQDOOLVW >%\WH@
This signal list ends with an end identifier with a value of "0".
Optionally, other sizes and a list of the signals can be entered in the header area by SIMIT. You
can find additional information in section: Structure of the memory area (Page 164).
Note
You can create a maximum of 32 SHM couplings in one project.
%\WH
0'
0:
'DWDDUHD
Note
As the smallest unit of the memory area that can be addressed is 1 byte, 1 byte can only be
assigned either to an input signal or to an output signal. Binary signals with the same byte
address can therefore only be either all binary input signals or all binary output signals.
SIMIT also accesses the memory area with byte-by-byte rather than bit-by-bit write access. 1
bit in one byte of the memory area for which no binary input signal is defined in the SHM
coupling is set to "0" upon SIMIT write access to the memory area.
The address name of a signal starts with "M" for "Memory" and then contains the data type and
address. Based on the address notation in SIMATIC automation systems, the data types set
out in the table below can be used.
The following applies for mapping the integer signals in SIMIT simulation projects to the data
types in the memory area:
● The least significant byte (LSB) of the signal is used for the BYTE data type.
● The WORD and DWORD data types are unsigned and the INT and DINT data types are
signed. The values are limited to the value ranges specified in the table above.
The structure of a floating-point number is governed by the "IEEE Standard for Binary Floating
Point Arithmetic" (ANSI/IEEE Std 754-1985).
● Symbol name
The signal is identified by this name in SIMIT.
● Address
Signal values are stored in the data area of the shared memory area under this byte
address. The address "0" corresponds to the first byte after the header area.
● Data type
The data type specifies the space a signal occupies in the data area and how the signal
values saved there are to be interpreted. The options are as follows:
– Logical value
– Signed integer value
– Unsigned value
– Floating-point number
● Comment
The comment is used to document the signal. It is not evaluated.
● Time slice
Here you set the cycle at which the coupling exchanges data. The assignment of absolute
cycle times to the 8 available time slices is valid for the entire project. Time slice 2 is the
default, corresponding to a cycle of 100 ms.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
Note
If you activate the "Signal description in header" option, the size of the header area is
determined by SIMIT based on the input/output signals in the coupling. The "Header size"
property is not editable in this case.
● Big/Little Endian
This property determines the byte order in which values of the WORD, INT, DWORD and
DINT data types are encoded in the data area.
Note
If you open the signal table for editing in Excel, all cells must be formatted as "text" so that Excel
does not make any unwanted format conversions.
Note
To use the PRODAVE coupling you also need version 6.2 of the SIMATIC PRODAVE software.
This software is not included in the SIMIT product package. You may also need additional
hardware, such as MPI adapters or connecting cables. These also are not included in the SIMIT
product package.
The PRODAVE coupling does not simulate any SIMATIC I/Os. SIMIT directly addresses the
process image of a SIMATIC controller via the PRODAVE coupling. The addresses that are
actually addressable depend on the size of the CPU process image and on what was defined
in your hardware configuration.
6,0$7,&
FRQWUROOHU
&38 ,2PRGXOHV
3URFHVVLPDJH
6,0,7ಥ352'$9(*DWHZD\
Note
Do not use any I/O modules connected to your controller that use the same address ranges as
the PRODAVE coupling. They will otherwise compete for access to the process image.
Note
If you have configured I/O modules in HW Config, you can access the address ranges from the
PRODAVE coupling provided the configured modules are not actually connected. This will
cause access errors in the CPU, which you can catch by creating the corresponding OBs in the
control program. Because the PRODAVE coupling only has access to the process image, you
cannot access any simulated signals that are addressed in the CPU as I/O signals (PIW, PQW).
Some SIMATIC controllers such as CPU 313C have fixed connections to I/O modules whose
address ranges cannot be changed. These address ranges cannot be accessed via the
PRODAVE coupling.
● Time slice
The cycle in which the coupling exchanges data is set here. The assignment of absolute
cycle times to the 8 possible time slices applies to the entire project. Time slice 2, which
corresponds to a cycle of 100 ms, is preset.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
● Mnemonics
Here, you select whether the international (I/Q) or German (E/A) mnemonics are to be used
for the inputs and outputs.
● CPU slot
Enter the slot number of your SIMATIC CPU here.
● Access mode
Here, you select whether to you want to use MPI (cable or adapter) or IP (Ethernet) access.
● MPI address / IP address
Enter the MPI number / IP address of the SIMATIC CPU here.
Additional functions
See also
"Exporting signal properties" dialog box (Page 935)
Method of operation
With the MCD coupling, SIMIT communicates with a Mechatronics Concept Designer
application over a software interface of SIEMENS NX. SIMIT uses the MCDcoupling for cyclic
exchange of data from the signal pool and the technological objects of the coupled MCD
application. The coupling to exactly one MCD application is supported.
6,0,7 0&'
,QWHUIDFH
6LHPHQV1;
Operating principle
You need the following couplings in SIMIT to simulate the control of a Mechatronics Concept
Designer application:
● Couplings to a controller of the SIMATIC family
● MCD coupling
The figure below shows the simulation of a control schematically using a position change of a
robot axis as an example:
3ODQW
352),1(7
WDUJHW Q Q
3RVLWLRQ
DFWXDO
6,0,7
&RXSOLQJWR &RXSOLQJWR
&38 0&'
The "Coupling to CPU" transfers the control command to the PROFIdrive component. The
PROFIdrive component calculates the target position based on the control command. The
target position is transferred over the MCD coupling to the Mechatronics Concept Designer
application. The Mechatronics Concept Designer application contains the CAD model of the
robot and its physical properties, such as the weight. Using a physics engine for modeling the
physical conditions, the Mechatronics Concept Designer application calculates the actual
movement of the component. Then the Mechatronics Concept Designer application returns the
calculated actual position.
Control loop
If you have configured a system with isochronous mode and you want to simulate isochronous
mode, use PLCSIM Advanced. Otherwise, use PLCSIM, Virtual Controller or SIMIT Unit.
6\VWHPFRQILJXUHGZLWK
LVRFKURQRXVPRGH 12
3/&6,0
<(6
9LUWXDO
&RQWUROOHU
6LPXODWHLVRFKURQRXV
PRGH 12 6,0,78QLW
<(6
3/&6,0$GYDQFHG
PLCSIM Advanced, SIMIT and MCD correspond to PLC, SINAMICS and robot in the plant.
Introduction
In a SIMIT project, you can create a coupling of the type "MCD".
Requirement
● The project is opened in SIMIT.
● Mechatronics Concept Designer version 11.0 or higher is installed on the SIMIT PC.
Note that a coupling to Mechatronics Concept Designer version 12.0 requires at least
service pack 1 (version 12.01).
Procedure
To create a coupling of the type "MCD", follow these steps:
1. Add a new coupling in the project tree under "Couplings".
The "Selection" dialog box opens.
2. Activate the coupling type "MCD".
Result
The coupling of the type "MCD" is created in the project tree.
Requirement
● The project is opened in SIMIT.
● A coupling of the type "MCD" has been created.
Procedure
To import an MCD application and its signals, follow these steps:
1. Double-click the coupling of the type "MCD" in the project tree.
The coupling editor of the MCD coupling opens.
2. Start the signal import by clicking the "Import" button in the menu bar of the coupling editor.
The "MCD Select Part File" dialog box opens.
3. Select your MCD application in the main file.
4. To import the MCD application and its signals, click on "Import".
Result
The MCD application including all referenced files is copied completely to the SIMIT project.
The signals contained in the MCD application are created in the SIMIT signal pool.
Requirement
● The project is opened in SIMIT.
● A coupling of the type "MCD" has been created.
Procedure
To link an MCD application and its signals, follow these steps:
1. Double-click the coupling of the type "MCD" in the project tree.
The coupling editor of the MCD coupling opens.
2. Start the signal linking by clicking the "Link to" button in the menu bar of the coupling editor.
The "MCD Select Part File" dialog box opens.
3. Select your MCD application in the main file.
4. To link the MCD application and its signals, click on "Link to".
Result
The signals contained in the MCD application are created in the SIMIT signal pool. The files
referenced by the MCD application still remain at their original storage location.
Introduction
The coupling of the type "MCD" permits a configuration of the physical unit of each exchanged
signal. The configured physical unit is valid for use within the simulation model in SIMIT. The
physical unit of the same signal in the MCD application can certainly be different.
Requirement
● The project is opened in SIMIT.
● A coupling of the type "MCD" has been created.
● SIEMENS NX in version 12.0.1 or higher is installed on the SIMIT PC.
Procedure
To configure the physical unit of signal of the MCD coupling, follow these steps:
1. Double-click the coupling of the type "MCD" in the project tree.
The coupling editor of the MCD coupling opens.
2. Select the desired signal in the "Input/output signal" area of the coupling editor.
The signal is highlighted.
Result
The physical unit of the desired signal of the MCD coupling was changed.
Requirement
● MCD coupling has been created.
● "Bus synchronous" operating mode is set.
● A time slice with the configured cycle time from STEP 7 is configured.
Procedure
To configure a bus synchronous MCD coupling, follow these steps:
1. Double-click on "MCD coupling" in the project tree under "Couplings".
2. Configure the MCD coupling in the property view:
– Select the time slice that is configured with the cycle time from STEP 7.
– Activate the "Bus synchronous" option.
Result
The bus synchronous MCD coupling is configured.
Time slice
Here you set the cycle at which the coupling exchanges data. The assignment of absolute cycle
times to the 8 available time slices is valid for the entire project. Time slice 2 is the default,
corresponding to a cycle of 100 ms.
Note
The time slice with the lowest cycle time always has the highest priority, regardless of the
numbering.
Bus synchronous
Specifies whether the MCD application is synchronized with the SIMIT model calculation.
When you set bus synchronous here, you must configure the parameterized cycle time in the
selected time slice.
When you set bus synchronous here, you must also set bus synchronous in the project
manager in the property view. For more information about the bus-synchronous operating
mode, please visit Operating modes (Page 42).
2XWSXWVLJQDO
IRUH[DPSOH$ ,QSXWVLJQDO
IRUH[DPSOH(
6,0,7
All signals contained in a coupling are listed in the coupling editor. Access to a signal from the
coupling is with the symbol name or the absolute address, irrespective of how the signal is used.
Signal names therefore remain unique throughout the entire SIMIT project, even if the same
symbol name or the same address occurs in several different couplings.
Note
Each coupling within a SIMIT project must have a unique name.
For example, if you want to connect SIMIT to multiple PROFIBUS DP masters, create a
separate coupling and assign a unique coupling name for each PROFIBUS DP master system.
This ensures that all coupling signals are assigned to the correct coupling.
● Every additional click on the column header toggles between alphabetically ascending and
descending sort order. The arrow changes its direction:
– for sorting in ascending order
– for sorting in descending order
● To further reduce the number of signals displayed, you can also set a filter in each column.
In this case, only signals that meet all filter criteria are displayed.
In the figure below, a text filter for the address of signals is set:
Introduction
Signals can be set and "fixed" at a specific value. With fixation, the signal values currently
pending are applied first to achieve a smooth switchover.
There is an automatically generated control for each signal to display fixation in the coupling
editor:
"Toggle switch with fixation" for signals of the data type "binary"
"Digital input with fixation" for signals of the data types "analog" and "integer"
Note
Retaining a specific signal state is known as "forcing" in a SIMATIC controller. Fixing in SIMIT
is a comparable function, but only applies within the simulation model and does not cause
"forcing" in the SIMATIC controller.
For each coupling signal, the controls with fixation are available in the first column after starting
the simulation:
Symbol Meaning
Fixation switch is not active; the current value of the signal is displayed
Fixation switch is active; the fixed value is displayed and can be used
Input and display field for values of the data types "analog" and "integer"
If the fixation switch and/or the value cannot be operated, the corresponding symbol appears
on a gray background, for example if the coupling signal is not used in the simulation model.
The figure below shows how a toggle switch with fixation works:
$FWXDOYDOXH
(IIHFWLYHYDOXH
Override is basically a changeover, which either transfers the actual value in the coupling or
changes it to a value that is input manually. It is possible both with input and with output signals
i.e. all I/O signals can be specified.
Example of fixation
In the example below, two signals are configured in the coupling and used in a chart in the
following way:
In the coupling you can see which value the controller outputs for the signal Q0.0.
Value output by the Q0.0 in the coupling Value used in the simulation model
controller
0 0
1 1
Override allows you to control your simulation model so that it uses a different value from the
one output by the I/O. To do this, click on the fixation switch for the signal Q0.0. This is then
shown like this: . You can now use the toggle switch to directly enter the value to be used in
your simulation model as follows:
Value output by the Q0.0 in the coupling Value used in the simulation model
controller
0 or 1 1
0 or 1 0
The same applies to the input signals. For an input signal I0.0 you can first of all see what value
the simulation model outputs to the controller:
Using fixation, you can set the value that is output at the controller irrespective of the value
calculated in the simulation model. Enter the default value using the fixation switch:
This procedure applies in the same way to analog and integer signals. Only the default values
are entered with a digital input, unlike the binary values. A digital display is used in place of the
binary display.
See also
Fixing a signal (Page 206)
SIMATIC data type SIMATIC value range SIMIT data type Mapping to SIMATIC data types
BOOL true, false Binary true, false
BYTE 0 .. 255 Integer [ −128 .. 255 ]
WORD 0 .. 65535 Integer [ −32768 .. 65535 ]
(without scaling)
INT −32768 .. 32767 Integer [ −32768 .. 65535 ]
DWORD 0 .. 4294967295 Integer [ −2147483648 .. 4294967295 ]
DINT −2147483648 .. Integer [ −2147483648 .. 4294967295 ]
2147483647
REAL ±1.175495 × 10−38 Analog ±1.175495 × 10−38
±3.402823 × 1038 ±3.402823 × 1038
Values that are read in the SIMIT coupling, are applied to the SIMIT data types according to the
value range of the SIMATIC data types listed above.
All values output by SIMIT through the coupling that are within the SIMATIC value range are
output unchanged by SIMIT. Values outside this range are limited to the interval specified in the
last column and mapped to the data width of the corresponding SIMATIC data type. Negative
figures are saved as two's complement. For example, the figure −1 is transferred as a byte with
the same bit pattern as the figure 255.
Scaled signals are dealt with slightly differently. Raw values that are read into the SIMIT
coupling are limited to the value range of the SIMATIC and then converted to physical values.
Values output by SIMIT through the coupling are converted to raw values and then limited to the
SIMATIC value range:
SIMATIC data type SIMATIC value range SIMIT data type Mapping to SIMATIC data types
WORD [ −32768 .. 32767 ] Analog [ −32768 .. 32767 ]
(bipolar scaling)
WORD [ −32768 .. 32767 ] Analog [ −32768 .. 32767 ]
(unipolar scaling)
WORD [ −32768 .. 32767 ] Analog [ −32768 .. 32767 ]
(user-specific scaling)
You can find additional information on this in section: Scaling analog signals (Page 190).
This access is not carried out by cyclic communication between the controller and signals that
are listed in the coupling editor, but through components which are triggered to start a read or
write process. The required component types can be found in the basic library in the directory
COMMUNICATION | SIMATIC.
You can easily link the component with corresponding coupling by entering, in the properties
window of the unit connector, the name of the coupling that you want to access with that
component. Alternatively, you can create the unit connector using drag & drop by dragging the
module to be addressed from the property view of the coupling to the chart.
To use this access method for a coupling, you must have already saved the coupling. Open the
coupling in the editor, define, for example, an input or output signal and then save the coupling.
Access to a data record in the distributed I/O is possible with both PROFIBUS and PROFINET.
An example of use of the unit connector can be found in Linking SIWAREXU components to the
coupling (Page 525).
Data record communication is integrated by default in the following components. You
interconnect the Unit input directly with a unit connector:
● SIWAREXU components (Page 523)
● ASM452 – Interface module for identification systems (Page 867)
● ASM454 – Interface module for identification systems (Page 869)
● ASM456 – Interface module for identification systems (Page 871)
● ASM473 – Interface module for identification systems (Page 874)
● ASM475 – Interface module for identification systems (Page 877)
● ASM754 – Interface module for identification systems (Page 880)
● ASM850 – Interface module for identification systems (Page 882)
● ASM854 – Interface module for identification systems (Page 884)
● RF170C – Interface module for identification systems (Page 886)
● RF180C – Interface module for identification systems (Page 889)
See also
ReadMemory – Reading a bit memory address area (Page 545)
WriteMemory – Writing to a bit memory address area (Page 545)
ReadDatablock – Reading a data block (Page 546)
WriteDatablock – Writing to a data block (Page 547)
ReadDataRecord – Reading a data record (Page 548)
WriteDataRecord – Writing a data record (Page 548)
Unit connector (Page 393)
Data record communication (Page 122)
Introduction
The signals that belong to an imported configuration are automatically created in the coupling
when system blocks are imported. The system differentiates between binary signals with the
data width "Bit" and signals with the data width "Byte", Word (2 bytes), Double Word (4 bytes)
and others.
You can change the data width, for example by combining eight consecutive binary signals in
one byte signal.
You can only convert signals that have been created in the coupling as a result of the import of
system blocks. The address areas are set by the configuration. They cannot be changed, not
even by converting the signal data width.
Converting signals
The table below shows how you can convert signals:
● Combining signals: Read a table row from left to right
● Splitting a signal: Read a table row from right to left
Number Data type Data width Number Data type Data width
of signals of signals
8 BOOL 1 bit ↔ 1 BYTE 1 byte
2 BYTE 1 byte ↔ 1 WORD (INT) 2 bytes
2 WORD (INT) 2 bytes ↔ 1 DWORD (DINT, 4 bytes
REAL)
See also
Splitting a signal (Page 204)
Combining signals (Page 205)
As all analog modules in the SIMATIC module range that are transferred as a word operate with
a resolution of 2 bytes, scaling and descaling in SIMIT is only available for analog values of the
data type WORD.
The figure below shows scaling for unipolar and bipolar measurements:
/RZHUOLPLW
0HDVXUHGYDOXHV 0HDVXUHGYDOXHV
5DZYDOXHV 5DZYDOXHV
PDQLSXODWHG PDQLSXODWHG
YDULDEOHV YDULDEOHV
8QLSRODUVFDOLQJUHVFDOLQJ %LSRODUVFDOLQJUHVFDOLQJ
For types 1 and 2, the "Lower scale value" and the "Upper scale value" are preset with 0 or −100
and 100. These values can, however, be adapted to the measurement or setting ranges.
Unipolar and bipolar scaling (types 1 and 2) and the "User-defined" type (type 3) can also be
used as descaling for output signals.
Scaling types 4 to 18 can only be used as scaling for temperature measurements for input
signals.
Note
For the temperature measurement signals in a coupling, the measuring range limits are only
displayed. They cannot be edited.
High and low raw values can only be edited if the scaling type "User-defined" has been selected.
Note
This function is not available with the Virtual Controller coupling.
Note
The changes only apply to the simulation in progress. They are not automatically applied to the
configuration.
See also
Signal table (Page 195)
Scaling signals (Page 208)
Note
Please note that in seq format, the comment is limited to 40 characters and no data types are
included.
When seq format is imported to SIMIT, data words are always assigned the data type WORD
and double words the data type DWORD. Changes to data types INT or REAL must then be
made manually.
The import of the symbol table is supported by all SIMATIC couplings in SIMIT.
Note
The asc format uses fixed column widths. If you edit this file with a text editor other than the
symbol editor, you must not change the number of characters per line.
Note
The signal table has been revised with the SIMIT version 8.1 and expanded with column
headings. If you import a signal table that was created with a previous version of SIMIT, you will
need to modify it accordingly.
Due to the new "Custom" scaling type, the significance of the type numbers for scaling has
moved.
Note
If you edit a signal table in EXCEL, all columns must be formatted as "text" to ensure that
EXCEL does not carry out any unwanted format conversions.
Keyword Meaning
[AIN] Analog input signals
[IIN] Integer input signals
[BIN] Binary input signals
[AOUT] Analog output signals
[IOUT] Integer output signals
[BOUT] Binary output signals
Each keyword must be in a separate row. This is followed by the signal names to be assigned
to this section. The order of sectors is arbitrary. Not all sections must be used.
In each section, the signal table contains a single line per signal. The signals and their
properties are exported in quotation marks and separated by a semicolon.
If a row contains only a signal name without quotation marks when the signal table is imported,
the signal will be imported with that name, without comments and with the defaults.
Note
With an OPC client, the import format of SIMIT V8.1 is not backwards compatible with older
versions of SIMIT. If you have specified the multiplier or the readback capability in existing
import files, you must now add 2 additional empty columns for the implicit interconnection.
Introduction
You can import signal properties from the following files:
● Symbol table
● Variable table
● Signal table
● INI file
Requirement
● Project is open.
● Import file is available.
● Coupling has been created.
● Coupling editor is open.
Procedure
Follow these steps to import signal properties:
1. In the coupling editor, open the dialog box for importing signal properties.
2. Select the format of the import file.
3. Select the import file.
4. Select the signal properties you want to import.
5. Over "Mode", select what is to happen to the properties of existing signals.
6. If required, select "Adapt data width".
7. Click "Import".
Result
The properties are imported.
See also
"Importing signal properties" dialog box (Page 932)
Requirement
● Project is open.
● Coupling has been created.
● Coupling editor is open.
Procedure
Follow these steps to export signal properties:
1. In the coupling editor, open the dialog box for exporting signal properties.
2. Select the format of the export file.
3. Select the storage location of the export file.
4. Select the signal properties you want to export.
5. Click "Export".
Result
The properties are exported.
See also
"Exporting signal properties" dialog box (Page 935)
The I/O connectors can now be connected as required to the I/O of another component.
To enter the signal name, simply click on the I/O connector to select it and enter the name of
the coupling and the signal name in the property view.
Note
The name of the I/O connector must be written exactly as it is entered in the configurator.
Therefore, pay attention to upper/lower case and do not use spaces in address names such
as I0.0.
You can drag-and-drop the signals from the "Signals" task card.
You can also use I/O signals directly in other controls, such as a pushbutton.
Enter the name of the I/O in the property screen of the control or drag-and-drop the I/O signal
from the "Signals" task card to the property view of the control.
You can find more information on trends in: Trends (Page 280).
An I/O output connector can only be used once in an entire project. The following
interconnection would result in an error when the simulation project is started:
Introduction
An interconnection is the exchange of signals between two objects:
● Two coupling signals
● One coupling signal and the input or output of a component
Requirement
● Coupling has been created.
● Coupling editor is open.
Procedure
Follow these steps to interconnect signals:
1. Select the signal.
2. Enter the connection destination under "Connection" in the signal properties.
Result
The signal is interconnected.
Introduction
If you split a signal, its symbolic name is removed.
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
● Coupling editor is open.
● The signal to be split:
– Has been imported from a system block
– Is not fail-safe
Procedure
Follow these steps to split a signal:
1. Select a signal with one of the following data types from the signal table:
– BOOL
– WORD
– DWORD
2. Select "Split" from the shortcut menu.
Result
The signal is split into up to eight signals in line with the data type.
See also
Converting the data width of signals (Page 189)
Introduction
When you combine signals, their symbolic names are removed.
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
● Coupling editor is open.
● Signals to be combined:
– Have been imported from system blocks
– Are located in the same module
– Are not fail-safe
Procedure
Follow these steps to combine signals:
1. Select consecutive signals from the signal table:
– Data type BOOL: 8 signals
– Data type BYTE or WORD: 2 signals
2. Select "Combine" from the shortcut menu.
Result
The signals are combined.
See also
Converting the data width of signals (Page 189)
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
– PLCSIM
– PLCSIM Advanced
– PRODAVE
Procedure
Follow these steps to preassign a value to a signal:
1. Open the coupling editor.
2. Allocate the signal under "Inputs > Default":
– Analog signal: Enter the required value.
– Binary signal: Select the check box.
Result
The signal is preassigned the specified value when simulation is launched. The value can
change during the course of simulation.
See also
Fixing a signal (Page 206)
Introduction
In the coupling editor, you can set signals and display signal values while simulation is running.
Requirement
● Coupling has been created.
● Simulation has started.
● Coupling editor is open.
Procedure
Follow these steps to fix a signal:
1. Either enter a value or select the check box in line with the data type of the signal.
2. Select the fixing switch.
Result
The value of the signal is fixed. The value is not changed during simulation.
See also
Fixing signals in the coupling editor (Page 184)
Preassigning signals (Page 206)
Introduction
In SIMIT, signals are by default uniquely identified with their address. As the address says little
about the function of a signal, you can with some couplings assign a descriptive symbolic name
for a signal. Addresses or symbolic names are, for example, displayed at input and output
connectors.
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
– PLCSIM
– PLCSIM Advanced
– PRODAVE
Procedure
Follow these steps to address a signal symbolically:
1. Open the coupling editor.
2. Under "Symbol name", enter a symbolic name for the signal.
3. Select the "Options > Assign coupling signals" menu command.
Result
The identification of the signal has been switched from absolute addressing to symbolic
addressing. In SIMIT, you can now only access the signal using its symbolic name.
See also
Options > Assign coupling signals (Page 925)
Introduction
You can enter scaling values in the signal table instead of in the properties of a signal.
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
– PLCSIM
– PLCSIM Advanced
– PRODAVE
● Signal is analog.
● Signal is of the data type WORD.
Procedure
Follow these steps to scale a signal:
1. Open the coupling editor.
2. Select the signal.
3. Configure the scaling values in the signal properties under "Scaling":
– Select the scaling type.
– Enter the lower and upper physical value.
Result
Scaling for the signal has been defined.
See also
Signal table (Page 195)
Scaling analog signals (Page 190)
Transferring scaling to another signal (Page 209)
Introduction
You can transfer scaling from one signal to one or more other signals. Scaling is transferred in
the coupling editor column by column.
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
– PLCSIM
– PLCSIM Advanced
– PRODAVE
● Coupling editor is open.
● Signal has been scaled.
● A scaling type is set at the destination signal.
Procedure
Follow these steps to transfer the scaling to another signal:
1. Select the signal from the "Scaling" column.
2. Select "Copy cell" from the shortcut menu.
3. Select the destination signal from the "Scaling" column.
4. Select "Paste to cell" from the shortcut menu.
Result
The scaling is transferred to the destination signal:
● Scaling type
● Lower and upper physical value
See also
Scaling signals (Page 208)
Introduction
You can define a limit range for all analog coupling signals. Values outside this range many not
be transferred to the coupling partner or the simulation depending on the signal:
● Limit range for input signal: Coupling partner
● Limit range for output signal: Simulation
Requirement
● Project is open.
● One of the following coupling types has been created:
– SIMIT Unit
– Virtual controller
– PLCSIM
– PLCSIM Advanced
– PRODAVE
● Signal is of the SIMIT data type "analog":
– Standardized measured value (WORD)
– Floating-point number (REAL)
Procedure
Follow these steps to limit a signal:
1. Open the coupling editor.
2. Select the signal.
3. Configure the limits in the signal properties under "Limits":
– Activate the limits.
– Enter the lower and upper physical value.
Result
A limit range is defined for the signal. You can disable or change the limits while simulation is
running.
Note
When you read OPC signals, all signals in the coupling editor are overwritten. If you have input
cycle multiplier or comments at signals, for example, export the signals before reading. Once
you have read the signals from the OPC server, import the signals again.
Requirement
● Project is open.
● One of the following coupling types has been created:
– OPC DA client
– OPC UA client
● Connection to OPC sever is configured.
● OPC server can be accessed in the network.
Procedure
Follow these steps to read signals from an OPC server:
1. Open the coupling editor for the OPC client coupling.
2. Import the OPC signals with "Browse".
Result
The OPC signals are read from the OPC server. Only OPC signals whose data types are
supported by SIMIT are entered. Whether a signal is created as "Input" or "Output" depends on
the configuration of the signal on the OPC server.
See also
Mapping of signals and data types of an OPC server (Page 150)
Configuring an OPC DA client coupling (Page 153)
Configuring an OPC UA client coupling (Page 160)
Introduction
Signals transferred from SIMIT to an OPC server need not necessarily be accepted and applied
by the OPC server. To make the value that is actually effective in the OPC server available in
the simulation model, configure the signal as "With readback capability".
Requirement
● Project is open.
● One of the following coupling types has been created:
– OPC DA client
– OPC UA client
● Coupling editor is open.
● Signal is configured as "ReadWriteable" at the OPC server.
● Signal has been crated under "Inputs" in the coupling editor.
Procedure
Follow these steps to configure a signal as "With readback capability":
1. Select the signal.
2. In the properties of the signal, select the "Signal with readback capability" option.
Result
The signal is configured "With readback capability". You can use the input signal in an output
connector to read the value that is actually effective on the OPC server.
● Value that is sent to the OPC server by SIMIT:
3.1.2 Versioning
The version number is automatically included in the simulation project. It consists of several
elements:
● License number (e.g. AB12345)
● Time stamp (resolution is approx. 38 seconds)
● Major version (0 - 127)
● Minor version (0 - 999)
If the simulation project was changed, the version number is updated automatically the next
time the simulation is started.
If the simulation project has been changed but has not been started since then, an asterisk
appears after the version number.
The minor version is incremented to a maximum of 999; it then jumps back to 0 and the major
version is incremented by 1. You can also increment the major version manually by clicking the
"..." button. When you increment manually, a message appears that you need to confirm. The
project is then compiled and the new version identifier entered.
Note
If you create a new simulation project or open or retrieve a simulation project created with a
previous version of SIMIT, the version is set to "unversioned". The version is set automatically
once the simulation is started.
OPEN-LOG "C:\\Logfile.txt"
PRINTF "project version: %s", "_ProjectVersion"
CLOSE-LOG
Note
The minimum size for a diagram is 20 × 20 pixels.
The figure below shows an example of a component with input and output connectors in the
chart editor.
① Output connector
② Component
③ Input connector
Connecting I/O
Proceed as follows to connect I/O:
1. Position the mouse pointer over the I/O to be connected.
If the cursor display changes, a connection is possible at this point.
2. Click on the I/O to be connected.
3. Position the mouse pointer over the connection partner.
4. Click the left mouse button again.
The connection is now established and is shown by a connecting line.
Alternatively, you can hold down the mouse button to drag a connection from one I/O to another.
Connecting connectors
The input and output signals of the controller are managed in the couplings. These signals are
shown on charts by connectors:
● Output signal by green output connectors
● Input signals by red input connectors
You can drag-and-drop input and output connectors from the coupling to charts. Follow these
steps:
1. Split the work area with the menu command "Window > Split horizontally".
2. Open the coupling and the chart.
3. Drag the signal of interest from the coupling onto the chart by grabbing the signal at the left
border of the coupling and pressing the <Shift> key.
4. Connect the connector I/O to the I/O of a component.
Note
The coupling configuration must first be saved before a signal can be extracted from it.
You can alternatively also drag the input and output connectors from the "Signals" task card to
a chart. You can find additional information on this in section: "Signals" task card (Page 233).
Static graphic
To use a static graphic, drag-and-drop the required graphic element from the "Graphics" task
card to the chart editor. You can find additional information on this in section: "Graphic" task
card (Page 229).
Edit the graphic element with the functions provided in the chart editor toolbar:
When a graphic object is selected, a selection frame is displayed (as shown in the figure above
under (a)). You can change the size and angle of the graphic element using the superimposed
blue squares as follows:
● Move the mouse cursor over a square until its appearance changes as shown in the figure
above under (d). With the mouse button pressed, drag the graphic element to the desired
size.
● You can also rotate the graphic element by any desired angle with the upper blue point.
Move the mouse cursor over the blue point until its appearance changes as shown in the
figure above under (b). With the mouse button pressed, rotate the graphic element to the
required angle.
● You can move the angle of rotation as required (figure above under (c)).
Changing lines
Both endpoints of a line can be moved, whether for a simple straight line or for a line segment
within a polyline. Follow these steps:
1. Select the line.
A small rectangle appears at each end of the line.
2. Move the mouse cursor over an endpoint until its appearance changes as shown in the
figure above.
3. You can now move the endpoint while pressing the left mouse button.
You can follow the same procedure to move the endpoints of curved lines, in other words the
endpoints of elliptical arcs or the points of a Bezier curve:
Animated graphic
Animations can be created for each graphic element. For example, if you draw a rectangle, you
can see the "Animations" property in the properties view of the rectangle.
You can create a new animation for the selected graphic element by double-clicking "New
animation".
A dialog box opens and you can choose from the following animations:
● Movement
The graphic element moves in the chart.
● Rotation
The graphic element rotates around the axis of rotation.
● Scaling
The graphic element changes size.
● Visibility
The graphic element is shown and hidden.
● Image change
Image files are shown in the graphic element.
● Image sequence
An image sequence of image files is shown in the graphic element.
You may define several animations for a single graphic element and can both move and scale
an object, for example. Image change and image sequence are, however, mutually exclusive.
If you select the "Movement" animation, a copy of the graphic element appears offset from the
original object. A red arrow connects the copy to the original element as shown in the figure
above under (a). This red arrow visualizes the movement of the object.
Use the mouse to move the copy to the required target position.
The figure above under (b) shows the movement and target position for a horizontal movement.
In the properties view (see figure below), enter the signal that supplies the values for the
movement.
● To do this, simply drag the signal from the "Signals" task card into the property field.
● Enter the initial value and end value.
If you then start the simulation and change the signal value, the graphic element is moved
horizontally.
For signal values within the range specified by the initial and end values, movement takes place
along the specified arrow; for signal values outside the defined range, the movement continues
in a straight line beyond the arrow. The arrow thus specifies the direction of the linear
movement; the initial and end values only define the scale of the graphic element in the chart.
Several movement animations for a graphic object are superimposed and thus allow for
movement along curved paths.
For a group of several graphic objects, you can animate either the group as a whole or each
individual graphic object within the group.
The current signal name and a signal isolator are also displayed.
A signal can also be displayed simultaneously with several controls, for example, with a digital
display and an analog display. You can obtain a digital display by dragging the signal from the
coupling or the task card and deleting the signal splitter.
To generate the digital display and the analog display, drag the corresponding control from the
"Controls" task card onto the diagram.
You can find additional information in section: "Controls" task card (Page 226).
Either you enter the signal name manually, or it is generated by dragging and dropping the
signal from the "Signals" task card to the property view.
Basic components
This is where you will find the component types of the basic library. The basic library is created
when SIMIT is installed. The component types in the basic library cannot be changed and no
component types can be added. The component types in the basic library can, however, be
saved as copies in the "User components" and "Project components" areas.
You can find additional information on this in section: Basic library (Page 375).
Note
Adding components used in the project to a library
You can insert components used in the project in the following areas with drag & drop:
● User components
● Project components
User components
This is where you will find the component types that you have created or that other people have
made available to you. If you store component types in the "Global components" area, they will
be available in every SIMIT project.
You open any library directory with the command and have access to the component types
stored in it. The command is used to remove a selected directory from this section.
If you create user component types with the CTE, you must save them either in a library
directory or in Global components so that they are available in SIMIT. SIMIT updates the "User
components" area automatically if you save a component type there with the component type
editor.
You can find additional information on creating user components in the "SIMIT – Component
Type Editor" help.
Project components
This is where you find the component types that you can use with the open SIMIT project. If you
archive the project, all component types in this section are archived with the project as the
project library. If the project is then retrieved, these component types are also available again.
You can move component types anywhere within the two "User components" and "Project
components" sections or add them as copies. The component types of the "Basic components"
section can only be added to the other two areas as copies.
Open component types with the "Open" command in the shortcut menu.
Preview
The following information is displayed for a selected component type in the preview for the
"Components" task card:
● Symbol
The basic symbol of the component type.
● Name
The name entered in the component type.
● Version
The version information entered in the component type.
● Library
The library information entered in the component type.
● UID
The unique identification automatically assigned to the component type.
● Simulation tags
The information entered in the component type regarding the number of simulation tags.
Display
You will find the following controls for displaying signal values here:
● Binary display (Page 554)
● Analog display (Page 555)
Input
You will find the following controls for entering signal values here:
● Pushbutton (Page 560)
● Pushbutton with image (Page 561)
● Switch (Page 562)
● Switch with image (Page 563)
● Step switch (Page 564)
● Step switch with image (Page 565)
● Digital input (Page 567)
● Slider (Page 569)
With the "with image" option, you can add images to the control on the chart. For example,
photographs give you a realistic representation of the controls.
Others
Here you will find the following additional controls:
● 3D Viewer control (Page 573)
● Signal splitter (Page 570)
● Action (Page 572)
The controls can be linked to all signals in the "Signals" task card. You can use controls to
display not just the input and output signals of couplings and components, but also status
values of components, and to set editable parameters while simulation is in progress.
You can find additional information in section: Visualizing signals (Page 222).
Basic macros
Here you find five macros that can be used as signal generators. They can be configured with
respect to time slice duration and amplitude and yield different signal patterns:
● Random
● Sawtooth
● Sine
● Square
● Triangle
Note
Adding macros used in the project to a library
You can insert macros used in the project in the following areas with drag & drop:
● User macros
● Project macros
User macros
You can create your own macro components here. These macro components are saved in the
work area of SIMIT and are therefore available for all projects. You use the " " symbol to open
the folders that contain the macro components. You use the " " symbol to close a selected
folder and remove it from this area.
Project macros
You can create your own macro components here. These macro components are stored in the
project folder. They are only available while this project is open. All macro components stored
here are archived with the project. Therefore they are available in the project again when you
retrieve the project.
Info
Here the name, version, library, UID and number of simulation tags of a selected macro
component are displayed.
Graphic elements
The various graphic elements are listed.
Drag-and-drop the required graphic element to the chart editor, where it is displayed and can
be edited. Symbols from the chart editor are available for editing.
You can find additional information in section: Visualizing a simulation (Page 29).
Info
You will find a brief description of the selected graphic element here.
Basic templates
This is where the templates are stored that are provided by SIMIT. The "PCS 7 Library"
directory contains the templates for the process tag types (templates) of the PCS 7 Library.
Templates that are adapted to the APL library (Advanced Process Library) of PCS 7 Vx.y can
be found in the template folder "PCS 7 AP Library Vxy".
You can copy basic templates to the sections "User templates" or "Project templates" with drag
& drop and edit them there.
User templates
Save the templates for your SIMIT installation here. These templates are then displayed in the
"Global templates" section. User libraries can be opened with the " " symbol and closed with
the " " symbol.
Project templates
The templates stored here are saved in the project and are archived with the project. After
opening or retrieving a project these templates are available again.
You can drag and drop or copy defaults within "My templates" and "Project templates".
You can find more information in Templates (Page 244).
Example:
1. Retrieve each of the 2 projects to project folders.
2. Open another project in SIMIT.
3. Open the project manager.
4. Click on the " " symbol in the "Projects" task card.
The "Open project" dialog box opens.
5. Navigate to the project folder of the open project and select the project file *.simit.
The project opens in read-only mode in the "Projects" task card.
You can now drag-and-drop individual elements such as charts or complete folders to the
project manager to create a copy in the current project as shown in the figure below:
You may also open individual charts from a project in the chart editor, copy parts of these charts
and paste them into charts in another project.
Close the projects in the task card by clicking on the " " symbol.
Info
If you have selected a signal, the origin, signal type and data type are displayed in the "Info"
area.
You can find additional information in the following sections:
● I/O signals for connection on charts (Page 200)
● Addressing a signal symbolically (Page 207)
① Sheet bar for inputs
② Sheet bar for outputs
The inputs and outputs of the macro are assigned to the cells in the sheet bars:
● Inputs in the left sheet bar
● Outputs in the right sheet bar
As with charts, you can use all components in the library and static graphics to model certain
responses in the macro component. Of the connector components, you may only use the global
and the topological connector.
You can find additional information in section: Topological connectors of macro components
(Page 238).
Controls and animations are not available in macro components. Macro components cannot be
hierarchically structured, which means you cannot insert any macro components into a macro
chart.
If you have created a chart already and want to use it to create a macro component, you can
copy the relevant parts of the chart and paste them to a macro chart. Only usable components
are pasted to the macro chart.
Note
Every connector must have a unique name. The name must contain only letters, digits and the
underscore character, and must start with a letter. The name is case sensitive.
Macro components containing errors are marked with the " " symbol.
Macro components with errors can be opened and edited in the editor, but you cannot use them
in charts. You can find an explanation of the errors on the "Diagnostics" tab of the editor
property view.
If macro components of this type are used in charts, the topological I/Os of the macro
component can be connected to topological I/Os of other components or other macro
components. The topological structures defined in the macro components are in this case
merely substructures of the overall topological structure of a flow or transport network.
Editing parameters
● Click on the " " symbol to set a parameter as a parameter of the macro component. This
moves the parameter from the component level to the macro component level.
The symbol changes to " ".
● In the text box to the left of the " " symbol, enter a name for the parameter (example in the
screenshot above: "SpeedSlow").
The parameter is then displayed in the macro component with this name.
● In the text box below the "Value" column, enter a suitable default setting (example in the
screenshot above: "30.0").
When the macro component is used in a chart, the parameters and their default settings are
now shown in the property view.
● Short name
The short name is displayed in the header in the instance of a macro component.
● Version
The version of a macro component can be freely assigned. It is displayed in the "Info"
section on the "Macros" task card and in the tooltip for the macro component in the chart.
● Library family
The library family of a macro component can be freely assigned. It is displayed in the "Info"
section on the "Macros" task card and in the tooltip for the macro component in the chart.
● Password
Macro components can be password protected. If a macro component is password
protected, it can be used on charts but cannot be opened without entering the correct
password. The last password entered to open password protected macros is saved until the
project is closed.
Note
Keep the passwords for your macro components in a safe place, otherwise you will not be
able to open even your own password-protected macro components.
● Width
The width of the symbol.
● Height
The height of the symbol.
You can use a macro component on a chart like any other component. It can be connected with
components and controls as well as with other macro components.
By double-clicking the macro component in the diagram, you open the macro chart in read-only
mode, which means you cannot make any changes to the macro chart.
Note
Retrieving or opening a SIMIT V7, SIMIT V8 or SIMIT V9 project in SIMIT V10.0 may take a very
long time the first time it is done.
Projects from older SIMIT versions cannot be used with SIMIT V10.0. Such projects must first
be opened with a SIMIT V8 version and migrated.
See also
Structure of the control file "procedure.cfg" for import from ZIP file (Page 270)
4.1 Templates
Templates prepare frequently recurring functions of a simulation model, for example parts of a
chart, in such as way that they can be used as a template for charts when you create new
projects. You can use all of the same elements in templates that you use in charts:
● Components
● Macro components
● Controls
● Graphics
In templates, unlike in charts, placeholders are used for various elements in the components in
the template. When a template is instantiated, a chart is generated in which the placeholders
are replaced with values, signal names, etc. You have the following options to instantiate
templates:
● Drag-and-drop the template to the project
● Importing files
● Using the simulation model
Proceed as follows to create templates:
1. Open the "Templates" task card in the project manager.
2. Open the template dialog to create a new template by double-clicking on " ".
3. Open a template for editing by double-clicking on the template in the task card.
4. Edit the template with the components, controls, macro components, graphics, templates
and projects available to you in the template editor resources.
Templates in the "Basic templates" area can only be opened for viewing in the template editor;
they cannot be edited. To indicate this the template is opened in the editor with a white title bar.
If you wish to edit a basic template, copy it to the "User templates" area.
The difference between templates and charts is that placeholders are used in templates.
Example:
1. Create a new plant template in the "Global templates" area.
2. Open the sample project "Elevator" in the "Projects" task card.
3. Open the "Main drive" chart.
4. Now copy the entire content of this chart into the open template.
In the properties of the PLCSIM V0 output connector, the input fields for both source
(coupling) and signal name now also contain the " " symbol for setting placeholders.
7. Now set corresponding placeholders for the other input and output signals and for the global
connector.
Make sure that you always use the same placeholder ("Coupling") for the input and output
signals.
The placeholder symbol allows you to define as placeholders: all inputs and parameters of
components and macro components, signals in controls and animations, and component
names.
For some controls you can also define the type, default setting and scaling as placeholders. The
table below shows which properties can be used as placeholders for controls.
Control Name Time slice Typ Default setting Scaling Connec‐ Objective
e tor
Button X X X
Button with image X X X
Switch X X X X
Switch with image X X X X
Step switch X X X
Step switch with im‐ X X X
age
Digital input X X X
Slider X X X X X
Bar graph display X X X X
Binary display X X X
Analog display X X X
Digital display X X X
Action X X
In some cases the type and default setting of controls take the form of language-dependent lists
in the user interface. If you define these properties as placeholders, you must specify the
position of the corresponding term in the list when making the replacement.
Type Value
NC contact 0
NO contact 1
After confirming the dialog you will see a new chart with the same name as the template in the
Project Manager. When you open the chart, you will see the instantiated simulation. It is
identical to the simulation of the main drive, except for the missing output signal Direction. The
output connector was not instantiated because it lacked a replacement. If you had deselected
"Remove elements with empty replacements" in the instantiation dialog, a connector with a
signal value i.e. an empty connector would have been generated in the instance.
The next steps will depend on whether or not Microsoft Excel is installed on your computer.
● Microsoft Excel installed
A new workbook is directly opened in Excel, with the entries needed for the selected
template already entered in the top row on the first sheet. Complete the table and save it in
a location of your choice for use in table import.
● Microsoft Excel not installed
An Excel file in *.xlsx format is created, with the entries needed for the selected template
already entered in the top row on the first sheet. Save this file in a location of your choice for
editing in Excel later – if necessary on another computer.
The first three columns of the generated tables contain the terms HIERARCHY, TEMPLATE
and CHART. The subsequent columns contain the names of the placeholders used in the
template. The name of the template is already entered in the second row, but you must enter
all other information yourself.
Note
Please note that when this table is imported, the profile is set to "Placeholders defined in 1st
row".
If such devices are used on templates, this information is not always available. Instead the
module start address may be known. Therefore it is now permissible to identify a module on
templates by its start address, for example, "IW512" or "AW512" instead of "[1][4][4]".
When the simulation is started it is necessary to know the address with the slave or device
number and the slot number. Therefore when a template is instantiated, a start address is
automatically converted to the address with the slave or device number and slot number. If
there is no coupling with the appropriate address when the template is instantiated, you can
also run the automatic conversion later with the command "Options > Assign coupling signals
(Page 925)".
is replaced as follows:
However, you can also start complete replacement subsequently at any time by calling the
function "Options > Assign coupling signals (Page 925)".
Note
Indirect addressing is only supported by the virtual controller and by the following couplings:
PROFIBUS DP, PROFINET IO, PRODAVE and PLCSIM.
Requirement
● SIMIT project is open.
Procedure
To instantiate the templates from files, follow these steps:
1. Select "Automatic model creation > Instantiate templates".
The "Instantiate templates" dialog box opens.
2. Select the "Import file" option.
3. Enter the storage location of the import file.
4. To import tables, follow these steps:
– To instantiate a template according to the table multiple times in a chart, select the
grouping to be made in the chart: horizontal or vertical.
– To line up the instances horizontally, enter the maximum width of the chart.
– To line up the instances vertically, enter the maximum height of the chart.
5. To import IEA files, follow these steps:
– Provide a name for the coupling to be used for I/O signals.
– Enter a template that matches the import file.
– Select the separator.
6. To import CMT files, follow these steps:
– Provide a name for the coupling to be used for I/O signals.
– Specify the folder in which the search for the SIMIT templates referenced in the CMT file
is to take place.
7. If necessary, deactivate individual chart folders, charts or replacements under "Preview>>".
8. To start the import, click the "Import" button.
Result
The templates were imported and instantiated from a file. The generated charts are stored in
the "Charts" folder.
See also
Table import (Page 252)
IEA import (Page 256)
CMT import (Page 258)
"Instantiate templates" dialog box (Page 938)
Note
If you still want to use files in *.csv format from projects in earlier versions of SIMIT, you must
convert them to this tab-separated *.txt format or to the *.xls or *.xlsx format.
Note
When importing a file in *.xls or *.xlsx format that is still open in Excel, it is the last saved version
of this file that is imported and not the currently open version.
Importing to SIMIT
The following options are available to perform a table import into SIMIT:
● In the portal view, select "Automatic model creation" > "Instantiate templates".
● From the Project view, select the menu command "Automatic model creation > Instantiate
templates".
● Select "Automatic model creation" > "Instantiate templates" from the shortcut menu of a
chart folder.
The first three columns have a pre-defined meaning and their headings are also pre-defined:
● Column A (HIERARCHY) defines the folder hierarchy to be created in the project.
● Column B (TEMPLATE) defines the template to be used.
● Column C (CHART) defines the name of the chart to be instantiated.
Starting with column D, the table may contain any number of additional columns with
replacements for the placeholders. The placeholder is given in the header of each column. In
this table profile, there are no restrictions in the number of placeholders.
Note
You specify templates (TEMPLATE) with the full folder hierarchy. Use the backslash '\' as the
separator. To refer to a template that is not located in any subfolder, enter the name of the
template preceded by a backslash.
If the template name is entered without separators, all folders and subfolders are searched for
a template with this name. Therefore, it is not permitted for two templates with the same name
to exist in different subfolders. The three panes of the "Templates" task card are searched in the
following order:
1. Project templates
2. User templates
3. Basic templates
If a chart is deselected in the left tree view, it is not instantiated. By selecting a folder, you can
also select or deselect multiple charts within it. You can tell from the check box whether a chart
or folder is selected ( ) or deselected ( ) or whether at least one check box in one of the
subfolders is deselected ( ).
In the right table, you can also select and deselect individual replacements. If you deselect a
replacement, it is as if the replacement were not in the table at all.
Importing to SIMIT
The following options are available to perform an IEA import into SIMIT:
● In the portal view, select "Automatic model creation" > "Instantiate templates".
● From the Project view, select the menu command "Automatic model creation > Instantiate
templates".
● Select "Automatic model creation" > "Instantiate templates" from the shortcut menu of a
chart folder.
The "Instantiate templates" dialog box opens.
Provide a name for the coupling to be used for I/O signals.
In the preview, you will see that a chart is instantiated for each CFC. This chart has the same
name as the CFC and is placed in a folder hierarchy that is identical to the folder hierarchy of
the PCS 7 project. You can decide whether to copy all information from the IEA file or deselect
specific replacements.
The following figure shows the template under (a) and the resulting instance under (b).
Now import the second sample file "VALVE00_Exp.IEA" for the VALVE template. This creates
additional charts in the SIMIT project in the folder hierarchy that was created during the first
import.
If you are using modified or user process tag types in your PCS 7 project, you can of course also
use these IEA files with corresponding SIMIT templates. Just create matching templates, in
"User templates", for example, or copy suitable basic templates and modify the copies.
Note
The "XML Transfer" function required for PCS 7 is not included in the product package of SIMIT
but can be obtained through SIOS (https://support.industry.siemens.com/cs/ww/en/view/
63481413):
1. Select category "PCS 7 Software Updates".
2. Select PCS 7 version
3. "Engineering System Collection" download Vx.y.
The "Engineering System Collection" contains several components, which you select via
the installation wizard. You only need the "XML Transfer" component for exclusive use with
SIMIT.
After the installation, the export can be performed directly from the PCS 7 project in the
SIMATIC Manager (from the technological view) using the shortcut menu command "Export
XML".
The exported XML file can now be imported into SIMIT to generate and test the instantiated
control module types in the simulation.
Importing to SIMIT
The following options are available to perform a CMT import into SIMIT:
● In the portal view, select "Automatic model creation" > "Instantiate templates".
● From the Project view, select the menu command "Automatic model creation > Instantiate
templates".
● Select "Automatic model creation" > "Instantiate templates" from the shortcut menu of a
chart folder.
The "Instantiate templates" dialog box opens.
After the templates are instantiated, the charts can no longer be identified as "template
instances", unlike in PCS 7. Therefore, it is not possible to subsequently switch versions or
retain customizations. Synchronization is not possible.
If the project changes in PCS 7, the XML file must be exported again and imported once more
into SIMIT. In this import, all the existing instances can be replaced with new charts. Individual
customizations that were made after the last CMT import to the charts already instantiated are
lost in the process.
Template creation
The following options are available in the Template Editor to define variables and placeholders
in the templates:
● A variable can be assigned to the value of a property field. For this purpose, the "{$}" symbol
to the right of it must be enabled. {$} means that the complete field content is interpreted as
a variable name.
● If more than one variable or fixed and variable components are to be combined, you can also
enter a variable name in the respective field using the notation {$ variable name}.
This enables you to specify replacements from the XML file in the instance of a template.
These components are assigned to the versions and their outputs are linked to the input of
another component with connectors. If one of the two CMTs is now omitted in the instance, the
corresponding component is also omitted in SIMIT and the connector remains unconnected on
a chart. Such connectors do not exist for SIMIT which means there is no double assignment that
would otherwise lead to a consistency error.
Introduction
Instantiation from the simulation model uses parameters of the components used in the
simulation model. Templates can be instantiated automatically for certain types of components,
for example, to create appropriate simulation of the control logic for process engineering
devices.
Requirement
● SIMIT project is open.
● The components in the project must contain the "TEMPLATE" and "HIERARCHY"
parameters.
Procedure
To instantiate the templates from the simulation model, follow these steps:
1. Select "Automatic model creation > Instantiate templates".
The "Instantiate templates" dialog box opens.
2. Select the "Simulation model" option.
3. Provide a name for the coupling to be used for I/O signals.
4. Specify the template folder in which the search for the referenced SIMIT templates is to take
place.
5. To start the import, click the "Import" button.
Result
The templates were instantiated.
See also
"Instantiate templates" dialog box (Page 938)
Introduction
The "Automated import" function supports the import of charts from the following sources:
● ZIP
Imports charts with referenced components, even if the components are not contained in the
SIMIT task card.
Applications such as COMOS can generate these import files. An import file is a ZIP archive.
● XML
Imports charts from an XML file. During import, existing templates for charts can be
instantiated and custom charts can be created without the need for templates.
The XML file contains a description of charts based on an XML syntax.
Note
In order to validate the XML file for correct syntax, run it through a validation with appropriate
tools before importing.
Requirement
● Project is open.
● A file suitable for automated import is available.
Procedure
Follow these steps to import charts from ZIP or XML files:
1. Start automated import using one of the above-mentioned commands.
The "Automated import" dialog opens.
2. To import charts from a ZIP file:
– Select "*.ZIP" as the file format.
– Select the required file.
Result
The data is imported.
See also
Syntax of the XML file (Page 263)
Examples for XML files (Page 268)
Structure of the control file "procedure.cfg" for import from ZIP file (Page 270)
The generic import interface can also be used to create an arbitrarily nested folder hierarchy.
The specified folder hierarchy in the import file is relative to the folder whose shortcut menu you
have selected to perform the import. This is the "Charts" system folder when the "Automatic
model creation" menu is used. If the import file contains no FOLDER elements, the templates
are created directly in the selected folder.
You can choose to instantiate individual templates (TEMPLATE) or combine multiple templates
in a chart (BUILDUP). In the template, enter the name of the template (NAME) and the name
of the chart to be created (INSTANCE) as attributes.
If you want to combine multiple templates to create a chart, you must enclose the template
elements in a BUILDUP element. In this case, the name of the chart to be created should be
specified in the BUILDUP element rather than in each individual template element:
Any number of replacements for placeholders can be specified within a template element using
the SUBST element.
Charts can also be created without using templates. To do this, use the DIAGRAM element:
The type of component is identified by the unique UID. For the component type to be
instantiated, it must be in a library, which means it must be available in the "Components" task
card.
You also need to specify the name (NAME) to be assigned to the component on the chart. If this
name already exists when it is imported into the project, SIMIT automatically adds a
consecutive number to make the name unique.
You only need to specify a reference name (REF) if the name of the component is not unique
within the import file and a connection to the component is to be specified. This can happen with
connectors, for example, which occur repeatedly with the same name.
The time slice to which this component is to be assigned can be specified with the CYCLE
element. If this attribute is not specified, a time slice value of 2 is entered.
Links to an existing component are described with the LINK element:
The position of a component or a link is specified by the POS element and its X and Y attributes.
The top left corner of the component is specified. The zero point of the chart is in the top left
corner of the chart. Positions must be positive and located within the dimensions of the chart:
A component can also be scaled and rotated with the TRANSFORM element:
The parameters or a component or a link can be specified with the PROP element and its
NAME and VALUE attributes:
Component connectors can be joined together. In some cases this takes place automatically if
they are superimposed on the chart and have the same connection type. In other cases the
connection has to be specified in the import file. Start by specifying the name of the I/O with the
PORT element:
The connection of directional signals should always be defined starting from the input, as the
input can only be connected to exactly one output of another component. Therefore the
connector to be specified in the connection definition is always the output of a component. As
topological connections are directionless, with this type of connection it makes no difference
which of the two connectors to be connected is specified as the connector in the connection
definition.
The SOURCE attribute contains the name of the component or coupling to be connected. The
NAME attribute contains the name of the I/O or signal. For connections of the type IMPLICIT,
the name of the component must be specified in the SOURCE attribute. Reference names
(REF) are not permitted for implicit connections in this case.
I/O default settings are specified with the DEFAULT element and its NAME and VALUE
attributes.
If no default settings are specified, the values defined in the component type apply for the
connectors.
In accordance with the usual XML conventions, comments are also permitted in the import file:
<!-- Comment -->
See also
Import charts from ZIP or XML files (Page 262)
4.3.4 Structure of the control file "procedure.cfg" for import from ZIP file
Introduction
The ZIP archive must contain the "procedure.cfg" control file at the top level. You use this
control file to define where the imported components are stored in SIMIT.
[GENERIC_IMPORT]
● file=<XML file>
Required. XML file that contains the import information.
● destination=<folder name>
Optional. Specifies the folder under "Project navigation > Charts" to which the components
are to be imported. If you do not make a setting here, the components are imported straight
to "Charts".
● RemoveEmptyElementsWithEmptyReplacement=<True | False>
Optional. Removes components containing empty replacements. The default is "False".
See also
Automatic modelling > Automated import (Page 924)
Import charts from ZIP or XML files (Page 262)
Introduction
You use bulk engineering to edit the parameters of a project in a table without opening
individual charts or components. You can export parameters and input defaults in a
spreadsheet (*.xlsx), edit the values and then import the content of the spreadsheet to the
project again. For structural changes to the simulation model, use the mechanisms for
automatic model generation.
Requirement
● SIMIT project is open.
● Project view is displayed.
Procedure
Follow these steps to export data:
1. Select the "Bulk engineering export" command from the "Charts" shortcut menu in the
project tree.
The command is available for the "project" and "chart" elements and for all elements below
charts.
If you run the export on elements below the "Charts" level, only the parameters and input
defaults of the components from that selected level on will be exported.
2. Enter a name for the export file.
Result
The export file is generated and saved in the specified directory.
See also
Automatic model creation (Page 243)
Introduction
You use the "Bulk engineering import" function to import the following data:
● Data exported and edited with the "Bulk engineering export" function
● Changed data from the last simulation run. The changes are saved in a file when you exit
the simulation.
Requirement
● SIMIT project is open.
● A file suitable for bulk import is available.
Procedure
Follow these steps to import data:
1. In the "Automatic modelling" menu, select the "Bulk engineering import" command.
The "Bulk engineering import" dialog will open.
2. If you want to import data from the last simulation run:
– Select the option "Apply changes from last simulation".
3. If you want to import data with the "Bulk engineering export" function:
– Disable the option "Apply changes from last simulation".
– Select the file from which you want to import the changed values.
4. If necessary, open the preview and select the elements that you want to import.
5. Start the import.
Result
The changed values are imported to the SIMIT project. If a parameter is outside a defined valid
range, the relevant maximum or minimum value is imported. Values with errors are not
imported.
See also
"Bulk engineering import" dialog box (Page 940)
Exporting messages
Export the messages by clicking on the " " symbol in the message editor. Export is in a text file
(*.txt). The text file has 4 columns:
● Simulation time
● Category
● Name of the triggering component
● Message text
The columns are tab-delimited.
The text file allows you to archive messages and edit them with a text editor.
Deleting messages
Delete all messages in the message editor by clicking on the " " symbol.
Hiding messages
A message component generates messages that are triggered by the binary signal to which it
is connected. When the signal changes from zero to one, a message is generated as an
"incoming" message; when the signal changes from one to zero, an "outgoing" message is
generated. "Outgoing" messages are indicated by parentheses around the message text.
A pair of messages consists of an "incoming" message and a subsequent "outgoing" message
for the same event. You can use the "Hide message pair" button to hide and show message
pairs. If you hide message pairs, the only messages that remain visible are those that have
"come in" but have not "gone out" yet.
Symbol
Function
The Message component type is to be found in the standard library Misc folder. A component
of this type will generate a message when the binary value at its input changes. In the case of
an "outgoing" message, the message text that is output by the component is placed in
parentheses.
You can specify the category and message text as parameters in the component property view.
Note
Messages in the SYSTEM category are system messages from SIMIT. Messages in the
ERROR category are messages from components in the basic library. When choosing
category names, avoid using SYSTEM and ERROR. When filtering messages by category, this
will allow to see just the messages from your own categories.
For example, a component of the type SQRT outputs the message "SQRT: invalid argument"
if the input value has become negative.
Messages from basic library components are always assigned to the ERROR message
category, and their message text is output in the format "Component type: Error message". All
messages are created as "incoming" or "outgoing".
A maximum of 4096 messages can be saved. If this limit is reached, the following message
appears:
5.1.3 Archive
The archive records the signals of a simulation run, which means from simulation start until
simulation stop. The next time simulation is run, i.e. the next time simulation is started, the
archive is cleared and the signals to be archived are once again recorded until the simulation
stops.
The following signals are recorded in the archive:
● Component input and output signals
● Component states
● Coupling input and output signals
Archived signals can be visualized as trends.
A deadband is defined in the archive editor to limit the quantity of data generated by recording
the signals. The deadband specifies how much a signal value must change before the value is
recorded. A signal value is only recorded if the value differs from the last recorded value by
more than the deadband. A deadband can only be specified for analog and integer signals. The
value of a binary signal is recorded every time it changes.
Note
If you enter a deadband of "0", a value is recorded in each cycle for analog and integer signals
that change continuously.
A maximum of 128 signals can be entered in the archive. If this limit is exceeded, an error
message is displayed.
Memory is reserved for each signal. With a basic cycle of 100 ms and a deadband of "0", a
signal is therefore recorded for about 2.5 hours. Less frequent signal changes result in longer
recording times.
5.1.4 Trends
Trends are stored in the "Monitoring" folder in the project navigation. Double-click on "New
trend" to create a new trend. You can create any number of trends in your project. You can
create and configure trends even if you have already started simulation.
Trends are opened in the trend editor within the work area. The trends of the signals are
displayed in the upper section of the trend window, and settings for the trend are made in the
lower section.
① Curve characteristics
② Settings
Note
It may be more difficult to compare multiple different signals in automatic mode because the
scaling continuously changes.
To specify fixed ranges, you can also enter the start value and end value separated by two dots,
for example: "0..2000".
If you want to label a signal in the trend with a name that differs from the signal name (which
consists of the source and name), you can assign an alias to the signal. This alias is used to
label the trend.
Note
You can create any number of trends in a project, but the total number of signals contained in
all open trends must not exceed 128.
Binary signals are displayed below the analog and integer signal trends. As binary signals can
only have the values zero (false) and one (true), a bar graph is used to show a binary signal over
the simulation time. A line represents a value of zero (false) and a bar a value of one (true), as
shown in the figure below:
7UXH )DOVH
Signals that are not archived are only plotted while the trend is open. This means the trend of
such signals is only shown from the time the trend was opened. If you stop a simulation in
progress, you will see only the signal trend of non-archived signals in trends that were already
open while the simulation was running. When a trend is closed, all of the recorded signals are
cleared. This means that the signal trends of non-archived signals can no longer be displayed
when the trend is reopened.
While the simulation is running the signal properties also display the current signal value.
The deadband of archived signals is taken into account in the display of signals in the trend. The
signal property view displays the dead band values while the simulation is running. For non-
archived signals, all values that are calculated in the simulation are recorded in trends.
Use the "Reset Y scaling" button to reset the Y axis to the defined ranges.
You can find additional information in section: Trend settings (Page 285).
Trend settings
Time axis
The scale of the time axis can be set with a slider:
The time at which the visualization starts is shown on the right hand side, below the time axis.
Add the corresponding number of days (d), hours (h), minutes (m) or seconds (s) according to
the measured values on the X axis to this start time.
The figure below shows a section of the time axis ranging from 31 minutes and 42 seconds to
31 minutes and 50 seconds.
Note
Refreshing the time display
The time axis moves from right to left and shows the seconds. The measuring point for the
minutes is the left-hand edge of the display. As soon as a value of 60 [s] passes the measuring
point, the minute counter is incremented by 1 and the scale values set back 60.
Cyclic update
When you open a trend and start the simulation, you will see the trend values in a constantly
updated sequence. The trends track the signals as they change. In order to obtain a static view
of the current trends, switch off the updating. To do so, deselect the update option:
If there is no simulation running, you see a static view of the recorded signals.
The trends for binary signals are always displayed in separate trends, one below the other, with
a single common time axis.
Printing trends
Proceed as follows to print a trend:
● Click on the " " symbol in the trend editor
The "Print" dialog box opens.
● In the dialog box, select one or more signals to be printed and then select "one above the
other" or "overlapping" signals under "Display".
You can find the other functions of the dialog box in section: "Print" dialog box (Page 942).
Exporting trends
Proceed as follows to export signals recorded in a trend to a text file (*.txt):
1. Click on the " " symbol in the trend editor
The "Export" dialog box opens.
2. Select the signals you want to export.
3. Give the export file a name under "File".
4. Click the "..." button to select a memory location for the export file.
5. Under "Resolution", select a time interval for the signals. The possible settings are 100 ms,
1 s, 10 s and 60 s.
The generated file will contain the points in time and the values for each signal, with one column
per signal. The individual columns are separated with the tabulator character. If there are
several signal values for an analog or integer signal within a time period, the arithmetic mean
between the minimum and maximum values that occurred is used.
You can find more information on the search function in: Find (Page 290).
You can find more information on the replace function in: Replace (Page 292).
Note
Find & replace in texts
You open the "Find" or "Replace" dialog box with the shortcuts <Ctrl+F> and <Ctrl+H>.
See also
"Find & replace" dialog box (Page 941)
5.2.1 Find
Note
Only saved data is searched; charts and couplings must therefore be saved before you search.
Select an element and click the "Find" button to launch the search.
You may be able to define additional search criteria and search options depending on the
element selected, for example a signal name for a signal search.
In the following figure, the system searched for components and macro components that
contain "CFC_NK114" in their name. The search in this case covers the entire project including
all subfolders, and is case-sensitive. You can view the results under "Search results": The
CFC_NK114 component.
Select a component or macro component under "Search results" to display the diagrams and
links that contain the component or macro component you are looking for under "Project
elements".
In the figure above, when you select "CFC_NK114" as the search result, the "CFC_NK114"
diagram is displayed under "Project elements". If you open the "CFC_NK114" diagram by
double-clicking, you can see that the component you are looking for is highlighted with a blue
frame.
If a search result corresponds to a single chart only, you can open the chart by double-clicking
on the search result.
To search for a specific signal, you can simply drag-and-drop it from the "Signals" task card to
either of the two text boxes.
When searching for a component type, enter its name and/or ID. Similarly, when searching for
a specific component type in your project, you can drag-and-drop a component type from the
"Components" task card to the input field.
To search for components and connectors, enter the name. With the search option "Output
connectors only", you can hide all search results of input connectors when searching for global
connectors and thus navigate directly to the respective output connector.
The Find & replace editor will then open with the search results.
Search results display and navigation are then as detailed in: Finding with the Find & replace
editor (Page 290).
As signals can only be fixed when simulation is running, this search option is only available after
the start of simulation.
5.2.2 Replace
Note
Replace only works with saved data. Charts and coupling must therefore be saved before the
replace function is launched.
● Enter the search criteria and options. Complete the "Replace with" text boxes and then click
"Find".
● Select the results that you want to replace in the search results. In line with the search
options set, you see the results of the replacement for each search result. As with the
search, all charts in which the signals for which you searched were found are shown under
"Project elements".
In your project, you can also replace components or macro components of a specific type by a
component or macro component of another type. The type and their UID are applied.
● Click the "Replace" button.
The "Assignments" dialog opens.
● The dialog shows the assignments of the inputs and outputs for both elements. The
assignment can be changed here.
● Click the "Replace" button to apply the assignments and launch the replace function.
5.2.2.2 Refresh
Refreshing components
The search criterion "Refresh" searches by component type for all components in the defined
search range that have the same name and belong to the same library family but were created
(saved) at a later time.
This updates the components in your simulation project in one operation. The search for current
component types is run in all component libraries in the "Components" task card in the following
order: "Project components", "User components" and "Basic components". The most recently
created component type is then suggested as the current type for replacement in the search
result.
"Refresh" works in the same way for all macro components in the defined search range; the
system search for current macro components in the libraries of the "Macros" task card. If all
components and macro components in the selected search range are already up to date, no
results are returned.
The "Refresh" option is also available if you want to update components by type in macro
components. Start the update via the shortcut menu for the macro component.
Inconsistencies are indicated by being preceded with the red symbol " ". Warnings are
indicated with the blue symbol " ". Using a command, you may switch the display on or off for
warnings.
In the above example there are two results:
1. There is no corresponding output connector for the "SPEED" input connector.
2. There is more than one "Incrementer" output connector.
The first message is only a warning and indicates that the simulation model may not yet be
finished. A warning will not keep you from launching the simulation. The second result indicates
an error that needs to be fixed before the simulation can be launched.
To fix an error or a warning select its entry in the list of results. The Project elements section
shows the charts in which the error or warning must be resolved. From this view you can then
open the charts to fix the problem. After resolving the inconsistencies, you may recheck the
project using the "Recheck" button.
Note
The consistency check only works with stored data. Data, charts and couplings must therefore
be saved beforehand.
The results of the consistency check can also be exported in a tab-separated text file. To do so,
activate the button in the consistency check editor as shown in the figure below.
Introduction
The SIMIT analysis function generates a statistical analysis from the data of a SIMIT project.
The statistical analysis is saved as an "*.xslx" analysis file. The following project data is
included in analysis:
● Couplings
● Components
● Macros
Capacities are also calculated for the following objects:
● Folder
● Couplings
● Charts
● Model size
● Scripts
① Capacities
② Statistical data
Requirement
● Project is open in SIMIT.
● Project view is displayed.
Procedure
1. Select the "Analysis" command from the shortcut menu in the project tree.
2. Enter a name for the analysis file.
If Excel is installed on the PC, the analysis file will immediately open in Excel.
Result
The analysis file is generated and saved in the specified directory.
8VHULQWHUIDFH
&UHDWHVLPXODWLRQRIIOLQH 5XQVLPXODWLRQRQOLQH
6WDUWVLPXODWLRQ 6WDUWLQJDVFULSW
6\QFKURQL]DWLRQ
6LPXODWLRQPRGHO ([HFXWDEOHVFULSW
&\FOLF 6HTXHQWLDO
6LJQDOVLQSXWVRXWSXWVVWDWHV
6HTXHQWLDOFRQWUROV\VWHP
Enter the time slice in which the script is to be executed in the Property view of the script editor.
If you include other scripts with an instruction, the time slice specified in the scripts included is
irrelevant; the applicable time slice is the one specified in the script that has been started.
If you enable the "Block interface" option, a dialog appears when the script is started that
prevents access over the interface to the simulation in progress. Close this dialog to cancel the
script.
A flashing symbol in the status bar indicates that a script has been started. The symbol
for simulation in progress is also displayed.
You can stop a script at any time using the shortcut menu for the "Scripting" folder.
Only one script can be run at a time. Execution of a script is stopped once all instructions in the
script have been completed, when it is stopped by a command or when the simulation is closed
or reinitialized in the interface.
After a script is started, the syntax is checked and the script is compiled into an executable
instruction list. Any error discovered in the script is signaled and the script is not started.
Problems can also arise that only become apparent once the script is being executed. Should
such problems occur, a message appears in the status bar and the script is stopped.
Note
We recommend that you only create and edit scripts using the SIMIT script editor, as this will
ensure that they remain in the simulation project. This is because only scripts located in the
SIMIT project tree can be executed and archived with the project.
However, if you wish to create scripts externally using a different editor, note the following:
Scripts are text files with the standard Windows character encoding (code page 1252). Script
files must have the file extension ".script". The script properties that are listed in the property
view of the script editor must be set as follows in the first two lines of the script file in line with
the information in the "Keywords for script properties" table:
Keyword = Value
Example:
META_BLOCKGUI = False
META_CYCLE = 2
Keyword Meaning
META_BLOCKGUI True: The user interface is blocked while the script is being executed
False: The user interface is not blocked while the script is being executed
META_CYCLE Cycle (1 to 8) in which the script is to run
You can find additional information in section: Composing scripts (Page 304).
Note
When you archive a project, only the scripts located in the simulation project are archived.
External scripts are not archived with the project. The archived project is therefore incomplete.
is used to cancel the processing of a script. If the BREAK instruction is used in an included
script, processing resumes in the calling script.
The instruction
QUIT
is used to terminate the script. If the QUIT instruction is in an included script, the calling script
will also be terminated.
Mode Button
"Yes" "No" "OK" "Cancel"
YESNOCANCEL X X – X
OKCANCEL – – X X
YESNO X X – –
OK – – X –
YESNOCANCEL is the default mode. Selecting "Cancel" in the dialog box terminates the script;
the simulation stays paused. In all other cases, the simulation is restarted and script execution
resumes.
In the example
DIALOG "Ready?" YESNOCANCEL
the dialog box shown in the following figure appears.
If a log file was already open in the script before the DIALOG instruction, the system records in
this file whether the dialog was closed with the "Yes" or "No" button. Based on this, the entry
DIALOG text True
or
Note
Once a script is started, an executable instruction list is created for this script and all the
included scripts. The included scripts must therefore exist before the calling script is started;
changes made to an included script after the calling script is started have no effect.
Note
When you archive a project, only the scripts located in the simulation project are archived.
External scripts are not archived with the project. The archived project is therefore incomplete.
A simulation is always in one of the following three states: "Offline", "Stopped" or "Running".
2IIOLQH
6LPXODWLRQ!6WDUW
6LPXODWLRQ!,QLWLDOL]H
6LPXODWLRQ!(QG
6723 67$57
6LPXODWLRQ!3DXVH 6LPXODWLRQ!6WDUW
6LPXODWLRQ!(QG
5XQQLQJ
The simulation state can be changed by a script. For example, the simulation can be stopped
and started again. However, script commands are only effective if the simulation state is
"Stopped" or "Running". Scripts cannot start an "Offline" simulation, nor can they end a
simulation.
This command is invalid if the simulation has already been started. In this case, the following
error message appears in the status bar and the script is terminated:
Wrong simulation state, Script '...', Row ... .
Note
The INIT script command cannot cause the transition from "Offline" to "Online", because a
script can only be executed in online mode.
Note
The START script command cannot cause the transition from "Offline" to "Online", because a
script can only be executed in online mode.
Starting with this command automatically sets the simulation time to real-time (100%).
is used to pause the execution of the script for n time slices. The time slices are counted in the
script time slice. For one cycle, i.e. for n=1, the parameter n can be left out.
If the simulation is initialized but has not yet been started, this command will cause the
simulation to begin.
Note
A simulation step is always one step of the fastest submodel, which means the submodel with
the shortest cycle time.
NOTICE
Data loss
Any snapshot with the same name that already exists in your simulation project will be
overwritten without a prompt and the data saved in it will be lost.
Note
Resetting the simulation time causes inconsistencies in the trends of the Trend and Messaging
Editor. This is because all the values in the trend are recorded over the simulation time.
6.3.6 Logging
You can log the results of your simulation, i.e. signal values or events. Script instructions can
be used to create log files in which outputs are documented.
Script instructions to output data are ignored if no log file is open when the script is executed.
Note
Any log file that already exists with the same name will be overwritten without warning. Data that
is already saved in the log file will be lost.
You must close the log file either at the end of the script or at the point where you no longer wish
to record any more data.
The instruction
CLOSE-LOG
closes the log file.
Note
The outputs are not saved in the log file if the log file was not closed by a instruction before the
end of a script. In this case, the log file is empty.
saves the current values of the signals listed in the instruction in the open log file. The
Formatstring contains the format specifier for each signal; it must contain precisely one format
specifier for each signal. The format string may also contain text. The allowed format specifiers
are listed in the table below.
A backslash must be placed in front of the percentage sign in the format string if you would like
the percentage sign to be output as a normal character: \%. Use the PRINTF instruction without
a signal specification if you want to output a fixed text only.
Signals can be any input signals, output signals, states or component parameters that can be
changed online. You can find additional information on this in the section: Signals in scripts
(Page 305).
In the example
PRINTF "Ramp: %.2f [ULR=%b] [LLR=%b]", "Ramp#1/Y", "Ramp#1/ULR",
"Ramp#1/LLR"
the following is output to the log file:
Ramp: 0.00 [ULR=False] [LLR=True]
Syntax Meaning
_t_day Day
_t_mon Month
_t_year Year
_t_hour Hour
_t_min Minute
_t_sec Second
Time: 12:55:13
Note
The system variables in the "System variables" table can only be used in the context of logging
and cannot be used for general calculations within the script.
Note
The SIMIT component type editor (CTE) is required to edit the behavior description of
component types. The component type editor is a SIMIT expansion module with which you can
create your own component types.
opens the plot file File name and starts to record the signals. The name of the file (File name)
must be specified with its absolute path, in which any backslashes must be doubled.
A plot file that is already open is closed first. If the file File name already exists, it will be
overwritten without confirmation.
Note
The signals to be recorded must be specified before the file is opened.
The first line of the plot file shows the signal names of the signals to be recorded. The remaining
rows contain the simulation time in milliseconds, and tab-delimited signal values in the
sequence that is specified in the first row.
The instruction
CLOSE-PLOT
closes the plot file and the list of signals to be recorded is deleted.
The instruction sequence
STOP
INIT
START
PLOT "Ramp#2/Y"
PLOT "Ramp#2/ULR"
PLOT-CYCLE 500
OPEN-PLOT "D:\\plot.txt"
GO-FOR 4000
CLOSE-PLOT
would add the following to the plot file:
Ramp#2/Y Ramp#2/ULR
0 1.66666666666667 Ramp#2/ULR
500 18.3333333333333 False
1000 35.0 False
1500 51.6666666666667 False
2000 68.3333333333333 False
2500 85.0 False
3000 100.0 True
3500 100.0 True
4000 100.0 True
You can set input signals, status variables and parameters and components that can be
changed online with instructions in the script. You can also set these variables to pre-defined
values or apply a linear change to the values.
Note
If you set inputs that are linked to the outputs in the simulation project or give values for states
of a component that are set in the component itself, the value specified in the script will either
be completely ignored or will only be effective during one computing time slice.
Operator Meaning
() Parentheses
* Multiplication
/ Division
+ Addition
− Subtraction
Operator Meaning
() Parentheses
! not
&& and
|| or
The operators are listed in both tables from highest to lowest priority.
Example:
"Display/E" = 2 * ("Slider/A" + 0.5)
Note
A value that you have assigned to a signal will not be available until the next execution time
slice. If you have set a signal using an instruction in the script, for example, and you want to use
this signal to assign a value or output its value in the instruction that immediately follows, the
signal still has the value that it had at the beginning of the cycle.
There is no start value (FROM start) in the second instruction. The start value in this case is the
current value.
Script execution continues during the specified time time, which means other instructions in the
script are executed without waiting for the signal to reach its specified end value. A script is not
terminated until all signals that were set using ramps have reached their end values.
Examples:
RAMP "Display#1/X" FROM 20.0 TO 10.0 IN 15000
Basics
You can implement conditions for execution with the following instructions:
IF expression THEN
block1
ELSE
block2
ENDIF
If the condition expression is true, the instruction list block1 is executed; otherwise list block2 is
executed. The two instruction lists consist of one or more lines with any number of instructions,
and can therefore themselves contain conditional instructions.
The ELSE instruction can also be omitted:
IF expression THEN
block
ENDIF
Operator Meaning
< Less than
<= Less than or equal to
> Greater than
>= Greater than or equal to
== Equal to
!= Not equal to
A condition can consist of multiple expressions that are linked with Boolean operators. You can
find additional information on Boolean operators in the tables in: Setting individual values
(Page 314).
Examples
IF "Button#1/Z" THEN
"Display/E" = 2.0 * ("Slider/A" + 0.5)
ELSE
IF !"Button#2/Z" THEN
"Display/E" = 3.0 * ("Slider/A" + 0.5)
ELSE
"Display/E" = "Slider/A"
ENDIF
ENDIF
In the example below, "True" is returned if the value of the analog signal "TemperatureValue"
is between "0.5" and "1.25".
Note
The term 'component' is used in the CTE user interface instead of 'component type'.
All editors are opened in the work area. The tools window only contains the specific task cards
for each editor. There are menu commands that divide the work area horizontally (Window >
Split horizontally) or vertically (Window >Split vertically) so that two editors can be opened side
by side or one below the other in the work area.
The Signals task card allows you to filter by name, signal type and data type. It thus provides
a rapid overview of the signals available in this component type. You can also easily move a
signal name from the task card into the text editor using drag & drop.
Note
You can protect components you have created yourself with a password. You are prompted for
the password when you open such a component. Some components from the basic library are
protected when they leave the company and cannot be opened. You can find additional
information in section: Protection of the component type (Page 332).
You can find additional information on the properties of a component in section: Properties of
component types (Page 330).
The unique identifier (UID) of the enumeration type is also displayed in the preview.
In the behavior description, you use an element of an enumeration type by entering the name
of the enumeration type followed by a period and the name of the element itself. The entire
construct must also appear in single quotes, for example: 'ClosedOpen.Closed'.
You can use the basic connection types as the basis for your own connection types. To do this,
copy the connection type to the User connection types pane and edit it.
The unique identifier (UID) of the connection type is also displayed in the preview. Note that
connection types are only identical if they have the same UID. The name of the connection type
is not a sufficient criterion. Even connection types for which the same signals are defined do not
have to be identical.
This type-instance concept allows you to change a component type without having to change
the instances already created from it.
Note
After making changes to a component type, if you want to update the instances you have
already created in your simulation project, you simply use the Find&Replace function in SIMIT
to replace component types.
Every component instance is identified by a separate, unique name in SIMIT. Every instance
can be parameterized individually with respect to both the actual parameters, any preassigned
inputs and the symbol scaling.
7.2.3.1 Overview
General properties of a component type include
● Administration
● Protection
● Special features and
● Changes
of that component type. To edit the general properties open the corresponding editor by double-
clicking the aspect General in the project tree. You can then edit the individual properties, which
are presented in a fixed arrangement of groups of text boxes.
● Library identifier
● Library family
You can enter any name. It is used to display the component type in the SIMIT Components
task card. It is also used as the basis for automatically assigning a name when the component
type is instantiated on a chart. The name is independent of the file name under which the
component type is stored in the file system.
The version and library family of a component type can be defined arbitrarily.
This information is displayed in the Components task card preview in SIMIT, but is not
evaluated any further.
If you change the name or version of a component type, saving the component will
automatically open a file selection dialog so that you can also save the component under a new
file name. The default file name will match the component name.
Libraries that are included in the SIMIT product range have a predefined library ID. The library
ID is entered in every component type of a library. When you create user-defined components,
the library ID is automatically set to "0".
The Storage location of the component type in the file system and its unique identifier UID are
displayed for information.
Note
Keep the password in a safe place. You are not be able to open this component type in the
Component Type Editor without the right password, even if you have created it.
To set this property, use the Is graphically scalable option in the editor and specify which
connector can be scaled graphically.
The graphically scalable connection must be defined as a vector of connectors of which there
is a variable number, whereby the number must be created as a parameter of the type
dimension.
A component type may have other connectors in addition to the one that is graphically scalable.
However, the graphically scalable connector must always be positioned on its symbol below all
the other connectors.
● Direction
The direction defines whether the connector is defined in the IN or OUT direction. Binary,
integer and analog connectors are thus defined as inputs or outputs.
The special case of a connector without direction (NONE) is only of relevance in association
with special libraries. You can find further details in the manuals for these libraries.
● Number
If you have entered a value other than the default number one, you have defined a connector
vector with the specified number of elements. These connectors are simply numbered
consecutively in the component instance by appending an index number starting with one
to the name.
You can also enter a parameter as number that determines the number of connectors. This
parameter must then be of the type dimension.
● Default
Connectors that are defined as inputs can be given a default numerical value. This default
setting can be overwritten in every component instance.
Connectors also have other properties that can be defined in the properties window for every
connector:
● Usage
A connector can be used in different ways. The connector should generally be visible on a
chart at the component symbol so that it can be interconnected with other components. Set
the usage to Symbol and properties window to do this.
If you want the connector to only be visible in the properties window for a component, and
not on the component symbol on the chart, set the usage to Only in property view. This
connector will then be permanently identified as an invisible connector by the symbol in
the properties window for the component.
The In CTE only setting allows the connector to be used in the component type, but not to
be visible on the symbol or in the component properties window.
● Default visibility
If a connector has the usage Symbol and properties window, you can set whether it is initially
visible ( ) or invisible ( ) after instantiation on a chart.
● Implicitly interconnectable (for input signals only)
All connectors that have the usage Symbol and properties window can also be implicitly
connected in the properties window for the component instance. The Implicitly
interconnectable property is permanently set for this usage.
Here you can define whether connectors with the usage Only in property view should be
implicitly interconnectable connectors or not. If you set a connector with this usage to not be
implicitly interconnectable, only the default assignment for this connector can be overwritten
in the properties window for the component. If you set it to implicitly interconnectable, the
default for Value/Signal is changed to Signal.
● Default value/signal (for input signals only)
If the usage of the connector is set to Symbol and properties window, you can select whether
the connector is set to Value ( ) or Signal ( ) by default in the component instance.
If the default is Signal, the default visibility setting is automatically set to Not visible.
● Connector is moveable
You can define whether the connector in the component instance may be moved on the
outer edge of the component. Hold down the "Alt" key and drag the connector with the
mouse to move it.
● Comment
The comment for a connector is for documentation purposes only and is not evaluated by
SIMIT.
● Connection type ID
Because the name of a connection type does not have to be unique, the unique ID allows
you to identify it if there is any doubt.
The symbol for this input is then set to the signal name specified in the properties window for
an instance of the component. This input of the component is thus permanently interconnected
to the output of another component. In the sample signal shown in the figure above, the output
X1 is a component with the name ADD#5.
Rather than fixed names for the signal, you can also use parameters or the component instance
name. To do this, write the parameter name or _NAME for the instance name in curly brackets,
preceded by the $ character for the source and/or connector of the signal:
● {$Parameter name} or
● {$_NAME}.
The parameter name and _NAME are thus merely placeholders in the component type for the
values of Parameter value or Instance name that are assigned in the component instance. You
can also compose the signal name as required from placeholders and fixed names.
You may use the system variable _INDEX to define implicit connections for individual elements
of a vector. Use {$_INDEX}, as shown in the following figure, for example. When instantiating
the component this expression is replaced in each element by the element index, whereby the
index counting starts at one.
If the following values have been set for a component as shown in this example,
● Parameter MaxObjects is set to 2 and
● Parameter BaseName is set to "LifterBase#1"
it results in the following default values for the input vector XPosition:
● XPosition1: LifterBase#1 XPositionOut1
● XPosition2: LifterBase#1 XPositionOut2
&RQQHFWLRQYLHZ
&RPSRQHQW. &RPSRQHQW.
&RQQHFWRU$DV &RQQHFWRU%DV
RXWSXW LQSXW
7HFKQLFDOYLHZ
Connections of this type are provided as basic connection types in SIMIT. These types are
offered in the selection screen as analog, integer and binary.
The SIMIT connection concept has been extended compared to this basic concept: A
connection may be used to transfer multiple signals between connectors in both directions. The
direction of a signal thus can no longer be derived from the connected connectors, so it needs
to be defined as a forward or backward signal in the connection type. Forward signals are
transferred from an output to an input; backward signals are exactly the opposite. The diagram
for such a complex connection is depicted in the figure below.
&RQQHFWLRQYLHZ
&RPSRQHQW. &RPSRQHQW.
&RQQHFWRU$DV &RQQHFWRU%DV
RXWSXW LQSXW
7HFKQLFDOYLHZ
)RUZDUGVLJQDOV
&RPSRQHQW. &RPSRQHQW.
%DFNZDUGVLJQDOV
Thus both input and output signals can result from a connector of a complex connection type.
These signals are listed in the properties window of the connector, where default inputs can be
individually specified.
Divide the parameters into the "Primary" and "Secondary" tabs. This separates the parameters
into "important" and "less important" parameters. Important parameters are used, for example,
for assigning the component parameters. If you define secondary parameters here, SIMIT
takes this distinction into account in the properties window for the component instance. A
further category (Additional parameters, which contains the secondary parameters) will then
appear in the properties window in addition to the Parameters category.
● Number
If you have entered a value other than the default number one, you have defined a
parameter vector with the specified number of elements. These parameters are simply
numbered consecutively in the component instance by appending an index number starting
with one to the name.
You can also enter as the number another parameter that determines the number of this
parameter. This parameter must then be of the type dimension.
● Default
Parameters can be assigned a default numerical value.
Parameters also have other properties that you can edit in the properties window for that
parameter.
● Modifiable online
Modifiable online parameters are parameters that can be changed for a component
instance while a simulation is running.
Parameters of the type dimension are not modifiable online.
● Unit
The unit entered here only appears as an additional property of the parameter in the
properties window for the component instance.
● Comment
The comment for a parameter is for documentation purposes only and is not evaluated by
SIMIT.
All names of parameters and connectors must be unique, which means a connector must not
have the same name as a parameter and vice versa.
7.4.1 Introduction
The functional behavior of a component type is defined by state variables and the behavior
description. The behavior description is subdivided into the following aspects:
● Initialization
● Cyclic calculation
● Functions
The component type editor provides suitable editors for all aspects: a table editor for the states
and a text editor for the sub-aspects of the behavior description.
● Number
If you have entered a value other than the default number one, you have defined a state
vector with the specified number of elements. These states are simply numbered
consecutively in the component instance by appending an index number starting with one
to the name.
You can also enter as the number another parameter that determines the number of this
parameter. This parameter must then be of the type dimension.
State variables also have other properties that can be defined in the properties window for the
component type:
● Default
Every state variable has a default setting matching its type. This default setting can be
overwritten in the component instance.
● Only visible in CTE
Set this option if you do not want this state to be visible in the component properties window.
● Comment
The comment for a state variable is for documentation purposes only and is not evaluated
by SIMIT.
For ease of orientation, you can activate the Highlight syntax option in the properties window.
Important elements of the description syntax are then made easier to identify by different text
colors. The table below lists the colors used for the individual elements.
Element Color
Input signal Green
Output signal Red
State Olive green
Parameters Pink
Element Color
Text constant Brown
Keyword Blue
Comment Gray
Note
The use of highlight colors increases the computing power needed to update the user interface
of the text editor; the extra time needed is sometimes sufficient to cause a short delay while you
are typing. You may therefore find it useful to switch off the highlighting, at least temporarily, if
your texts are very long.
All three text editors offer a function for finding and replacing texts under the icon. You can
also call up this function using the Ctrl+F or Ctrl+H shortcuts. There are various options you can
use for searching, as shown in the figure below.
You can find additional information on behavior description in the section Syntax for the
behavior description (Page 354).
7.4.4 Topology
The topology description is only meaningful in association with the libraries CONTEC and
FLOWNET.
For more information on topological aspects, refer to the section Topological properties
(Page 893) The CONTEC library and in the section Topological properties (Page 773) The
FLOWNET library.
7.5.1 Introduction
A graphical representation of a component instance is created in the form of a basic symbol for
every component type. The basic symbol is displayed in the preview of the Components task
card. It represents every component instance on the chart.
Optionally a link view can be created for a component type. This provides additional access to
the component instance. It is also possible to define an operating window for a component type
that can be opened for every instance while the simulation is running to set and display
component values.
You can apply animations to graphical elements used for creating the basic and link symbol.
If there is a vector of inputs or outputs that has a fixed, which means not variable dimension,
each individual connector of that vector can be freely positioned.
Note
Changes in the connector editor do not appear in the symbol editor until you save the
component type or run an update from the toolbar ( ) or by pressing function key F5.
● Width
Here you can specify the Width of the basic symbol in pixels as a numerical value. You can
also move the left or right edge of the symbol area in the editor window by holding down the
left mouse button. The numerical value for the width is automatically corrected.
● Height
Here you can specify the Height of the basic symbol in pixels as a numerical value. You can
also hold down the left mouse button on the top or bottom edge of the symbol area in the
editor window to move it. The numerical value for the height will change automatically as you
do so.
● Horizontally scalable
The Horizontally scalable option is used to define whether the basic symbol for the
component instance should be scalable in the horizontal direction on a chart. Suitable
handles are then provided on the selection frame of the basic symbol.
● Vertically scalable
The Vertically scalable option is used to define whether the basic symbol for the component
instance should be scalable in the vertical direction on a chart. Suitable handles are then
provided on the selection frame of the basic symbol.
● Minimum width
The Minimum width of the basic symbol cannot be undershot when scaling the basic symbol
horizontally on the chart.
● Minimum height
The Minimum height of the basic symbol cannot be undershot when scaling the basic
symbol vertically on the chart.
● Is rotatable
This option defines whether the basic symbol can be rotated on a chart or not. If it is
rotatable, a suitable handle appears on the selection frame of the basic symbol.
● Draw border
This option allows you to define whether the basic symbol should appear with a black border.
Note
The Scale property is only available if you have licensed the CONTEC library in SIMIT.
7.5.2.5 Scalability
When creating your own conveyor technology component types you can also set a scale for the
basic symbol and the link in the CTE. This scale fulfills two purposes:
1. When modelling handling equipment, all dimensions and positions can be specified in
millimeters relative to the selected scale.
2. When modeling an object, the dimension which results from the selected scale in the CTE
is the predefined size with which the object is created in the material list.
Note
This function is only available if the CONTEC library has been licensed.
The following system variables permit access to the actual dimensions of a component in the
behavior description:
If you provide a link for a component type, you can create any number of links for an instance
of this component type on charts in your SIMIT project.
See also
Creating and editing charts (Page 217)
You can use all controls for the SIMIT basic library in an operating window. These controls are
provided on the Controls task card. You can drag these controls from the task card onto the
drawing surface of the editor and connect them to suitable input or output signals of the
component type.
The Graphic task card also provides the SIMIT graphic functions for graphically designing the
operating window. Note that graphic objects in the operating window cannot be animated.
The properties window contains further options for designing the operating window:
● Extended operating window
You can divide the operating window into two areas, for example, to separate frequently
used operator controls from those that are needed less often. To do this, activate
the Extended operating window option. The editor then contains another area for the
extended operating window. This area is just as wide as the area for the operating window,
and the height can be changed as required.
In the open operating window for a component instance, you can easily open the extended
operating window by clicking the bottom edge.
● Width
Here you can specify the width of the operating window in pixels as a numerical value. You
can also move the left or right edge of the window area in the editor by holding down the left
mouse button. The numerical value is updated automatically.
● Height
Here you can specify the height of the operating window in pixels as a numerical value. You
can also move the top or bottom edge of the window area in the editor by holding down the
left mouse button. The numerical value is updated automatically.
7.6.1 Overview
The behavior description for a component consists of a part that is executed once during
initialization and a part that is executed in every cyclic calculation step. The same description
syntax applies to both parts.
There are two different approaches to the behavior description for a component:
● Equation-oriented approach
The equation-oriented approach describes every new status value or output value as an
explicit function of the inputs, parameters and states. It is particularly suitable for modeling
physical contexts. This approach allows you to describe the change in continuous state
variables using common differential equations as well.
● Instruction-oriented approach
The instruction-oriented approach describes the calculation of new state variables or
outputs in the form of programming instructions that are processed sequentially in the
specified order. This approach is particularly suitable for modeling technical behavior.
The two approaches can also be combined in a component type.
7.6.3.1 Overview
In the equation-oriented approach, the syntax in which you set out the behavior of your
component type consists of relationships in the form of equations rather than instructions.
These equations explicitly describe how a state variable or an output is calculated from other
variables, for example as follows:
Output = Parameter * Input;
As a general rule:
● Every equation contains the equals sign.
● On the left of the equals sign is the variable that is being determined. On the right of the
equals sign are the variables that are read (explicit form of an equation).
● At the end of every equation there is a semicolon.
● Any variable may occur only once on the left of the equals sign, which means a variable may
only be determined once.
The following variables may appear on the left of the equals sign:
● Outputs
● States (for time-discrete states, only the new value; for continuous states, only the
differential, which means the change in value) and
● Local variables.
The following variables may appear on the right of the equals sign:
● Inputs
● States (only the differential may appear here for continuous states)
● Parameters
● Local variables and
● Constants.
The name of a local variable must contain only letters, digits and the underscore character, and
must start with a letter.
Local variables are used to save interim results that will be needed again in the same
processing step.
If you wish to access calculated values again in the next calculation step, always create time-
discrete state variables rather than local variables.
7.6.3.3 Constants
The constants you can use will depend on the data type of the result variable. The constants for
each data type are described in the table below.
The calculation order is automatically obtained from the analysis of the dependencies and, in
this case, is exactly the reverse of the order in the description.
However, SIMIT does not only analyze the equations within a single component instance, but
rather across all the component instances with their reciprocal links in your SIMIT project and
defines a suitable calculation order for the project. In the example below, multiplication is
always executed before addition because the product is needed for the addition.
Situations may occur in which no unambiguous calculation order can be determined. In the
example below, the input values of the two AND operations each depend on the output value
of the other operation. This feedback means that one of the two AND operations is always
calculated with a non-current input value, which means with a value originating from the
previous calculation cycle.
In such cases, the order in which the equations are processed is undefined. SIMIT always tries
to maximize the calculation order, that is, to sort as many equations as possible into one
sequence. Thus, in the above example, SIMIT always processes the "Switch – AND – NOT –
binary indicator" sequence in this order. It is, however, not defined whether the top or the
bottom sequence should be processed first.
7.6.3.5 Operators
The variables on the right of the equals sign can be linked to one another with operators. The
operators listed in the table below are permitted, depending on the data type.
You can query such a parameter in the behavior description by referencing the name of the
enumeration type followed by a dot and the corresponding list entry. For example:
A = {Initial_Value = ClosedOpen.Open: TRUE; ELSE FALSE};
7.6.3.8 Vectors
You can also define all inputs, outputs, parameters and states as vectors. You can then access
the elements of the vector in the behavior description as follows:
● Individual elements
To access an element of a vector, append the desired index in square brackets to the signal
name.
Note that the first element of the vector has the index 0. The index must be a constant, non-
negative integer value and must not exceed the number of elements that this vector has.
Example:
Output[2] = Input * 2.0;
● Area
You can specify an equation for multiple elements of a vector by entering a range:
Vector_name[Index1 TO Index2]
SIMIT solves this vector equation so that the two examples below are identical:
Example 1:
Output[0 TO 2] = 1.0;
Example 2:
Output[0] = 1.0;
Output[1] = 1.0;
Output[2] = 1.0;
When you want to refer to the index in a vector equation, you can specify an index variable:
Vector_name[Index_variable: Index1 TO Index2]
This index variable can then be used on the right side of the equation. It does not have to be
declared as an additional local variable but its name must be a single character.
Example:
Output[i:0 TO 2] = Input[i + 1];
In this case, the resolution into individual equations is as follows:
Output[0] = Input[1];
Output[1] = Input[2];
Output[2] = Input[3];
● Whole vector
If you want to extend the range to the whole vector, you can also write:
Vector_name[ALL]
or specify an index variable:
Vector_name[Index_variable: ALL]
● Vector of a complex variable
If a signal has a complex connection type, the index is specified in square brackets at the
end of the complete name.
Example:
X1.Re[3] = Y1.Im[1] * Y2.Im[2];
If the following values have been set for a component as shown in this example,
● Parameter MaxObjects is set to 2 and
● Parameter BaseName is set to "LifterBase#1"
it results in the following default values for the input vector XPosition:
● XPosition1: LifterBase#1 XPositionOut1
● XPosition2: LifterBase#1 XPositionOut2
function has no parameters, it is called with an empty parameter list. The table below lists all the
available mathematical standard functions.
Introduction
If you have defined an analog state of your component type as continuous, the behavior
description does not specify how this state is calculated. Rather it specifies from which
variables and how this state changes over time: The change of state is defined in the form of
a standard differential equation.
You can also describe multiple continuous states in your component type by differential
equations that are dependent on one another. This then yields, for example, the following
system of differential equations:
$Z1 = Z2 + Factor1 * Z3 – Input1;
$Z2 = Factor2 * Z1;
$Z3 = Z1 + Z2;
To solve such standard differential equation systems, SIMIT uses a numerical solution method
based on the Runge-Kutta-Merson method.
Like in the definition of the the calculation order, the SIMIT global view accesses the simulation
project in this case as well: SIMIT not only handles the differential equations of a component,
but all the differential equations of the entire simulation project in a closed manner, which
means the differential equation system of the entire simulation model is mapped onto the
numerical solution method.
Notation Access
Z Value from the previous computation cycle
@Z New value after integration of the state equation
#Z Corrected value that is to be used in the next computation cycle instead of @Z
Notation Access
Z Value from the previous computation cycle
@Z New value
7.6.4.1 Introduction
The instruction-oriented approach is used to formulate user functions or entire function blocks.
No equations are used within user-defined functions and blocks; these are replaced by
program commands that are executed in the defined order. The syntax is identical within the
function or block definition.
7.6.4.2 Functions
Functions are created in the Functions sub-aspect of the behavior description. Double-click
the Functions entry in the navigation bar to open the text editor provided.
A function consists of the following elements:
● The keyword FUNCTION,
● The function declaration
● The instruction part and
● The keyword END_FUNCTION.
Syntax:
FUNCTION Function_name (Data_type Output_variable1 [, Data_type
Output_variable2]) : (Data_type Input_variable1 [, Data_type
Input_variable2])
Instruction_part
END_FUNCTION
Only the basic data types binary, integer and analog are permitted as data types for the input
and output variables.
Example:
FUNCTION Trigonometry (analog y1, analog y2) :
(analog x1, analog x2, binary state)
if (state) {
y1 = _sin(x1);
y2 = _tan(x2);
}
else {
y1 = 0.0;
y2 = 0.0;
}
END_FUNCTION
This function can then be called as follows in the initialization part or in the cyclic calculation:
(Out1, Out2) = Trigonometry(In1, In2, In3);
7.6.4.3 Blocks
You can add as many blocks as you like to the initialization or cyclic calculation and use an
instruction-oriented behavior description within these blocks as with functions.
A block consists of the following elements:
● The keyword BLOCK,
● The instruction part and
● The keyword END_BLOCK.
Syntax:
BLOCK
Instruction_part
END_BLOCK
The instructions within a block are carried out in exactly the same order that you defined them.
The order in which the blocks are calculated as a whole, however, is determined by SIMIT
based on dependencies in the same way as for the equation-based approach. SIMIT analyzes
which variables of the behavior description are calculated within a block, that is, which are
changed and to which there is only read access.
If you change a variable in more than one block, for example, by setting an output variable in
two blocks, this creates a contradiction that SIMIT is unable to resolve. Multiple variable
definitions of this type are therefore not permitted.
These variables are then only valid within the block or the function in which they are defined.
The data types listed in the table below are permitted for these variables.
The name of a local variable must contain only letters, digits and the underscore character, and
must start with a letter.
Here again the local variables in the block are only used to save interim results that will be
needed again in the same processing step. If you wish to access calculated values again in the
next calculation step, always create time-discrete state variables rather than local variables.
7.6.4.5 Fields
You can also define local variables as fields (arrays):
Data_type Name[Dimension];
The dimension must be an integer constant. You can also define a field with values:
Data_type Name[] = {Value1, Value2, …};
In this case, the dimension is automatically obtained from the number of defined values. The
field elements are initialized with the values specified in the definition.
7.6.4.6 Constants
The constants you can use will depend on the data type of the result variable. The constants for
each data type are described in the table below.
7.6.4.7 Loops
DO loop
Syntax:
do
Instruction_list;
while (Condition);
Example:
i = 0;
do
{
i++;
v[i] = 5 * i;
}
while (i < 10)
FOR loop
Syntax:
for (Initialization; Termination_condition; Iteration)
Instruction list
You can assign initial values to variables in the initialization part. The variables must first have
been declared. The termination condition determines how many passes are made through the
loops. The iteration is always carried out at the end of the loop.
Example:
for (i = 0; i < 10; i++)
k = k + 1;
WHILE loop
Syntax:
while (Condition)
Instruction_list;
The instructions in the while loop are executed for as long as the condition is true.
Example:
i = 0;
while (i < 10)
{
k++
i++;
}
IF instruction
The IF instruction has the following syntax:
if (Condition)
Instruction_list;
else
Instruction_list;
The else branch is optional and is executed if the condition proves to be false.
SWITCH instruction
The SWITCH instruction is used to compare a variable with different constants.
Syntax:
switch (Variable)
{
case Constant1:
Instruction_list;
break;
case Constant2:
Instruction_list;
break;
[default:
Instruction_list;
break;]
}
You can create any number of case blocks. The keyword break is needed and acts as an end
marker for instruction lists. The default block is optional.
Example:
switch (Status)
{
case 0:
Output = Input;
break;
case 1:
Output = Factor * Input;
break;
case 2:
Output = -1 * Factor * Input;
break;
default:
Output = 0.0;
break;
}
The variable that is looked up in the switch instruction must be either an integer or an
enumeration type. If it is an enumeration type, the alternatives in the case instruction are given
in single quotes.
7.6.4.10 Operators
The following operators are available within the functions and blocks. In the table below they
are arranged in order from highest to lowest priority. Where several operators appear together
in a section, they have the same priority.
Operation Notation
Parentheses (expression)
Function call Function name (parameter list)
Increment I++
Decrement I−−
Increment ++I
Decrement −−I
Unary plus (sign) +Z
Arithmetic negation −Z
Bitwise complement ~I
Logical negation !B
Multiplication Z*Z
Division Z/Z
Modulo remainder Z%Z
Addition Z+Z
Subtraction Z−Z
Bitwise left shift I << J
Bitwise right shift I >> J
Less than comparison Z<Z
Greater than comparison Z>Z
Less than or equal to comparison Z <= Z
Greater than or equal to comparison Z >= Z
Equality Z == Z or B == B
Inequality Z != Z or B != B
Bitwise AND I&I
Bitwise exclusive OR I^I
Bitwise inclusive OR I|I
Logical AND B && B
Logical OR B || B
Conditional expression B ? Expression : Expression
Operation Notation
Simple assignment B = B or Z = Z
Composite assignments Z *= Z
Z /= Z
Z += Z
Z −= Z
I <<= J
I >>= J
I &= I
I ^= I
I |= I
The type of permitted operand is divided into the listed groups of the table below:
For all assignments it should be noted that it is not possible to assign from a larger to a smaller
data type. The table below lists the assignments that are permitted.
There are functions for rounding or truncating the integer component when converting the data
type. You can find additional information in the section:Function calls for mathematical
standard functions (Page 360).
Notation Access
Z Value from the previous computation cycle
@Z New value
In conveyor technology component types you may also use the system variables that are listed
in the table below. These variables allow you to evaluate the dimensions of a component in its
behavior description.
8.1.1 General
8.1.1.1 Introduction
The basic library of SIMIT contains elementary functions for creating simulations, i.e. for
modelling plant and machine behavior. These functions are provided in the form of component
types and controls. This following sections describe in detail the individual component types
and controls contained in the SIMIT basic library.
Every symbol has connectors with names and a label or graphic that clearly shows the function
of the component on charts (see the figure below). The symbols are designed so that the
function of both the component and the connectors can be understood intuitively.
① Labeling / graphics
② Output connector
③ Connector name
④ Input connector
Components are represented by the type-specific symbol in charts. Click on the relevant
symbol to select a component in a chart. A blue frame then appears around the symbol for the
selected component. Simply hold down the mouse button to drag the symbol and to move it
within the chart.
Some components have handles on the selection frame. These handles are used to change the
size of the symbol.
Components such as connectors have handles on the left and right of the selection frame as
shown in the figure below under (a). When you roll the cursor over the handles, its appearance
changes as shown in the figure below under (b). Hold down the left mouse button to move the
handles and thus change the width of the symbol as shown in the figure below under (c).
For components such as ADD, the selection frame has handles at the top and bottom. These
handles are used to adjust the height of the symbol to suit the number of inputs. Simply click on
the top or bottom gripper, hold down the left mouse button and drag it up or down.
The formula components have handles on all sides and at every corner of the selection frame.
These allow you to adjust both the width and the number of inputs. The handles at the corners
of the symbol allow you to make these two settings at the same time.
When the simulation starts, controls act as active elements and they are represented
accordingly as active controls by their symbols as seen in figure below under (b). If there is no
active simulation, the symbols represent passive controls and are displayed as such as seen
in figure below under (a).
Controls, like components, are represented by the type-specific symbol in charts. Simply click
on a symbol to select it. The symbol of the selected control then appears with a blue selection
frame; simply hold down the left mouse button to drag the symbol and move it within the chart.
Use the handles on the selection frame to change the size of the symbol.
< ; GW
7
can thus easily be assigned to connectors X, T and Y. Connectors are only given names in the
symbol if the function of that connector is not obvious.
All inputs and outputs are either binary (logical), analog or integer inputs or outputs. Complex
connector types are not used in the components of the Basic Library. One exception is the
PROFIdrive type connector that is used to connect the header component and the device-
specific component in the PROFIDRIVE library. The values of the binary inputs or outputs are
designated by zero and one or, alternatively, by False and True.
As with components, the connectors for controls are either binary (logical), analog or integer
inputs or outputs.
The connectors for controls and components can be connected to one another if the following
rules are observed:
1. Only inputs may be connected to outputs.
2. An output can only be connected to one input, while an input may be connected to multiple
outputs.
3. Connectors to be connected must be of the same type.
Connectors can be connected in different ways:
● Connecting line
● Overlapping connectors
● By implicit connections.
In the first two cases, the connection is made graphically in the work area of the chart editor.
The chart editor is designed so that the rules for connecting connectors defined above are
automatically followed.
Implicit connections are made by changing the settings in the properties of the inputs or outputs
of components to be connected.
to close the connection. When the connection is closed, the rubber band is automatically
replaced with a connecting line with right angles and the triangles of the connected connectors
are filled in with color, as shown in the figure below under (c).
To delete connecting lines, first click on the connecting line to be deleted. The connecting line
then changes to a thick blue line as in the figure below and can be deleted by going to "Edit >
Cut" in the menu bar or with the "Del" delete key.
Note
If the connectors do not become invisible when they are overlapping, the connectors are not of
the same type and thus cannot be connected.
Implicit connections
Implicit connections are made by changing the settings in the properties of the inputs and
outputs to be connected of components and/or controls. To do this, open the property view of
the component (see figure below) and follow these steps:
1. Make the input or output to be connected invisible ( ).
Click the or symbol to toggle between input visible and input invisible.
Note
An invisible input or output is not displayed on the symbol for the component and thus
cannot be connected to another output or input using connecting lines.
The procedure is the same for a control. Because a control does not allow you to select a value/
signal, the second step is omitted and the output to be connected may be entered directly after
toggling to invisible.
Double-click in the connector box to open the field for entering the value (see figure below). To
complete your input, either press Return or click in the chart outside the connector box.
To enter a value in the property view, navigate to the relevant input and click in the input field
to open it (see figure below). To complete your input, either press Return or click in the property
view outside the input field.
Input of True and 1 or False and 0 are equivalent for binary parameters. Binary values are
always displayed as True or False.
You can set inputs in the ways described above even when the simulation has started. In this
case, however, the input will only take effect for the duration of the started simulation, which
means modified input values are reset to their original values when the simulation ends.
The properties of components can be accessed in the properties window. To display the
properties of a component in the property view, right-click or left-click on the component. If a
simulation is running, you can only display the properties by right-clicking. The properties of a
component are divided into:
● General properties
● Properties of the inputs
● Properties of the outputs
● Parameters
● States
General properties
General properties of components are the name and the time slice of the component, the
unique identifier (UID) of the component type, the position of the component and the width and
height of the symbol.
The name must be unique for all components and controls used in the project, which means the
project must not contain multiple components and/or controls with the same name. When you
drag a component from the library onto a chart, it is automatically assigned a name. This name
is made up of the designation of the component type and a number for the component type that
is unique across the entire project.
Check the Show Name check box to display the name of the component on the chart.
In this case input values are always displayed instead of signals, and it is possible to set each
input value.
● Display On/Off
In the first column, the value at the input of the component can be shown ( ) or hidden
( ). When the simulation is started, the display is switched on for non-connected inputs and
switched off for connected inputs. The display cannot be switched on for invisible inputs.
The figure below shows a component in which the display is switched on for all input values,
which means even for values at connected inputs:
● Forcing input
In the fourth column you can switch forcing on ( ) or off ( ) for every connected input.
● Input value
The fifth column is used to display or set the input value.
1DPH 5HIHUHQFHV
9LVLELOLW\ ,PSOLFLWLQWHUFRQQHFWLRQ
● References
The third column is used to search for references, which means for objects that use this
output.
● Implicit interconnection
In the fourth column, you can set whether this output is to be implicitly connected.
● Display On/Off
In the first column, the value at the output of the component on the chart can be shown ( )
or hidden ( ). When the simulation starts, the display is switched off for all outputs. The
display cannot be switched on for invisible outputs. The figure below shows a component in
which the display is switched on for all output values.
● Forcing output
In the fourth column, you can switch forcing on ( ) or off ( ) for every connected output.
● Output value
The fifth column is used to display or set the output value.
If you select one or more components before executing the command, the switch applies only
to the selected components. If no components are selected, the switch applies to all
components on the chart.
Parameters
Each parameter is displayed with its name and value in the property view:
States
States are displayed with their name and initial values in the property view. When the simulation
is started, the current values are displayed for each state.
The vector elements can be expanded and collapsed. The figure below shows a vector with
collapsed elements.
For connectors with complex connection types an additional expandable and collapsible level
has been added.
Note
If you use the ERROR message category in your own messages which you generate using
the Message component from the Trend and Messaging Editor, for example, you will be unable
to distinguish between messages from components of the basic library and your own
messages based on the message category.
The properties of controls can be accessed in the property view. To display the properties of a
component in the property view, right-click or left-click on the component. If a simulation is
running, you can only display the properties by right-clicking. Each control has
● General properties and
● Properties for the connector.
Controls whose representation can be changed also have
● Properties for the view.
You can find additional information on this in section: Controls (Page 554).
General properties
General properties of controls are the name, the time slice, the unique identifier (UID), the
position as well as the width and height of the control.
The name must be unique for all components and controls used in the project, which means the
project must not contain multiple controls and/or components with the same name. When you
drag a control from the library onto a chart, it is automatically assigned a name. This name is
made up of the designation of the control and a number for the control that is unique across the
entire project.
Check the Show Name check box to display the name of the control on the chart.
Controls may also have other specific, general properties. You can find additional information
on this in the section: Controls (Page 554).
Properties of connectors
Connectors may be visible or invisible. The figure below shows the property view with the
connector of a control by way of example.
8.1.2 Connectors
The connectors of the basic library have the following shared characteristics:
● The connectors of the global connector and of the I/O connectors have no type. This means
the connectors assume the connection type of the connector of the connected component
or control.
Note
A type check, which means a check to identify whether the connections connected via
connectors are of the same type, is carried out automatically before the simulation is started.
If connectors are connected with connectors of an incorrect type, a corresponding message is
output by the consistency check and the start of the simulation is cancelled.
● The width of the connector symbol on a chart can be adjusted to match the length of the
connector name. To set the width of a connector, click on the symbol. A blue frame with
handles appears on the right and left of the frame (a). If you move the cursor by means of
a gripper, the shape of the cursor changes (b). Then press and hold down the left mouse
button to change the width by moving the mouse pointer to the to the left or right (c).
● The connector name is displayed in the connector symbol.
If the global connector is connected to the output of a component or control, the connector on
the right side of the connector disappears: the connector is now used as an output connector.
If the global connector is connected to the input of a component or control, the connector on the
left side of the connector disappears: the connector is now used as an input connector.
For a connection between an output connector and one or more input connectors, all of these
connectors receive the same name: the connector name.
Note
Global connector name must be unique in the entire simulation project.
If you drag the global connector from the library onto a chart, the connector is assigned a name
that consists of the term Connector and a unique sequence number. A connector name can be
entered directly in the symbol. Double-click on the connector to open the input box, then press
Return or click outside of the input box to confirm your input.
The connector name can also be entered in the property view. The connector name is the only
property of the global connector.
If you do not want the name of the coupling to be displayed on the chart, you may deselect the
option Display coupling name.
● PLCSIM Advanced
● PRODAVE
See also
Linking SIWAREXU components to the coupling (Page 525)
Access to a data record or memory area (Page 188)
Components for SIMATIC (Page 536)
Introduction
The four basic analog functions of Addition, Subtraction, Multiplication and Division, which
means the four basic arithmetic operations, are stored as component types in the AnalogBasic
directory of the Standard Library.
ADD – Addition
Symbol
Function
The ADD component type maps the sum of the analog values at the n inputs x1 to xn onto the
output y:
Q
\ [ L [ [ [Q
L
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to zero by default.
SUB - Subtraction
Symbol
Function
The SUB component type maps the difference between the analog values at the inputs x1
and x2 onto the output y according to
y = x1 − x2
All inputs are set to zero by default.
MUL - Multiplication
Symbol
Function
The MUL component type maps the product of the analog values at the n inputs x1 to xn onto
the output y:
Q
\ [
L
L [[[Q
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to one by default.
DIV – Division
Symbol
Function
The DIV component type maps the quotients of the analog values at the inputs x1 and x2 onto
the output y according to
y = x1 / x2
Input x1 is set to zero by default, while the divisor input x2 is set to one by default.
The value of the divisor x2 must not be zero. If the divisor becomes zero during the simulation,
the error message "DIV: division by zero" (message category ERROR) is generated and output
y is set to zero.
Symbol
Function
The component type AFormula allows the use of explicit algebraic functions. This function f
calculates a value in relation to the n input values xi. The function value is assigned to the
output y:
y = f(x1, ..., xn)
The number n of inputs can be varied between 1 and 32. Only the inputs that are available
according to the number currently set may be used in the formula.
The following operators are used in expressions formula:
Operator Function
+ Addition
− Subtraction
/ Division
* Multiplication
( Opening parenthesis
) Closing parenthesis
Numeric constant Floating point numbers, also in exponential notation
Function calls Standard mathematical functions
Note
When entering floating point numbers, use a decimal point (and not a comma).
Note
There is also no check in the formula component to determine whether the arguments of the
formula have valid values. If division by zero occurs during the simulation in the formula
calculation, output y has the value Inf. If an argument of a formula is undefined during the
simulation, as in the case of a division of zero by zero, output y has the value NaN (not a
number).
These irregular output values will then be propagated in the model in all values that depend on
this output. Your simulation will thus enter an undefined state. To avoid this situation, make sure
that the inputs of the formula component can only assume values that ensure the validity of the
arguments in the formula.
There is no check in the formula component to determine whether all the set inputs are used in
the specified formula.
The mathematical functions listed in the table below are available as standard mathematical
functions.
Formula Function
sqrt(x) \ [ ; x ≥0
fabs(x) y = |x|
exp(x) y = ex
pow(x, z) y = XZ;
log(x) Natural logarithm: y = ln(x); x > 0
log10(x) Common logarithm: y = lg(x); x > 0
ceil(x) Smallest integer greater than or equal to x
Formula Function
floor(x) Largest integer less than or equal to x
rand() Integral random value y, 0 ≤ y ≤ 32767
sin(x) y = sin(x); angle x in radians
cos(x) y = cos(x); angle x in radians
tan(x) y = tan(x); angle x in radians; x ≠±(2n+1)π/2
asin(x) y = arcsin(x); −π/2 ≤ y ≤ π/2
acos(x) y = arccos(x); 0 ≤y ≤ π
atan(x) y = arctan(x); −π/2 ≤ y ≤ π/2
atan2(z, x) y = arctan(x / z); −π ≤ z ≤ π
sinh(x) y = sinh(x); angle x in radians
cosh(x) y = cosh(x); angle x in radians
tanh(x) y = tanh(x); angle x in radians
Note
You can use the function y= rand() to generate random numbers y within a specified range
YMIN ≤ y ≤ YMAX using the formula YMIN + rand() * (YMAX–YMIN) / 32767.0.
Parameter
Average
Symbol
Function
The component type Average maps the average of the n inputs X1 to Xn at output Y.
The number of inputs n is variable and can be set to any value between 2 and 32. The default
value of all inputs is "0".
Arithmetic mean
The arithmetic mean is the sum of all inputs Xn divided by the number n.
Q
; ;
;Q
< Q ;L
L Q
Median
All inputs Xn are arranged in (ascending) order by value. The median is the value exactly in the
middle.
[ Q QXQJHUDGH
<
Q Q
[ [ Q JHUDGH
Geometric mean
The geometric mean is the nth root of the product of all inputs Xn.
; ; ; ;Q
Q Q
< L
L
If the product is negative, the error message "Average – geometric mean: the product of all
inputs is negative" (message category: ERROR) is generated and output Y is set to "0".
Parameter
Characteristic
Symbol
Function
The Characteristic component type is used to define the mapping of input value x onto output
value y defined by a characteristic:
y = fK(x)
Parameters
Define characteristic
In this editor a characteristic is defined by specifying n interpolation points (xi, yi), i = 1, ..., n and
by selecting the type of Interpolation between these interpolation points.
There may be any number n of interpolation points. The type of interpolation may be either
constant or linear, in which case, the characteristic will take the form of a step curve or a
polyline. Polyline is the default mode.
Outside the interpolation point range (the interpolation range), the output values y are
extrapolated.
For each of the two axes, which means for the horizontal x-axis and the vertical y-axis of the
characteristic chart, the following variables can be set in the properties of the chart:
● the minimum value and the maximum value,
● the scale division and
● the scale.
Both axes default to a linear scale with a scale division of ten, a minimum value of zero and a
maximum value of one hundred.
The scale may be set to either linear or logarithmic.
The characteristic function for n interpolation points is thus given as 0.0 for n = 0, y1 for n = 1 and
for n > 1 for the step curve using
\IRU [ ื [
\ \L IRU [ L [ ื [L L Q
\ IRU [ ! [
Q Q
\ \
\ [ [ IRU [ ื [
[ [
\L \L
\ \L [ [L IRU [ L [ ื [ L L Q
[ L [ L
\Q \Q
\ Q [ [Q IRU [ ! [Q
[ Q [ Q
Alternatively, you can also insert an interpolation point at the current position by using the
shortcut menu.
Symbol
Function
The component type Compare compares the analog inputs x1 and x2. The binary output b is set
to 1 if the relational expression is true – otherwise, b is set to 0.
The selected comparison operator is displayed in the component symbol.
The width of the symbol can be changed to slightly offset the">=" and "<=" comparison
operators from the right edge of the symbol.
In SIMIT, analog variables are mapped to variables of the type double. A direct comparison for
equality or inequality is therefore not useful. double variable equality is only possible within the
accuracy defined by the computer (machine accuracy). Equality can be checked using the
model illustrated in the figure below, for example.
Alternatively, a functionally identical model can be used, for example with the AFormula
formula block.
The difference between the two variables x1 and x2 is calculated. The amount of this difference
is then compared against a definable positive limit ε:
LI _[ [ _ ˢ
E
RWKHUZLVH
To check for inequality, only the "greater than" comparison should be used in the comparison
component in both of the illustrated models.
Note
You can create your own components to check for equivalence or non-equivalence based on
the explanatory notes provided above.
You can create macro components with the macro component editor, for example, or a
relational component extended to include these comparisons with the Component Type Editor
(CTE).
Parameter
LI [ [
E
RWKHUZLVH
● Less than or equal to comparison
(<=), which means
LI [ ื [
E
RWKHUZLVH
● Greater than comparison (>), which
means
LI [ ! [
E
RWKHUZLVH
● Greater than or equal to comparison
(>=), which means
LI [ ุ [
E
RWKHUZLVH
Symbol
Function
You use the component type DeadTime to provide a dead time element. The analog value at
input x is passed to output y with an adjustable delay.
A step change in the input value x from zero to one thus gives a curve for the output value y as
shown in the figure below:
Note
If you change the cycle time Δt in the project properties, the set dead times change accordingly.
In the component, the input values are saved and sent to the output after a delay according to
the selected dead time. Memory is allocated for n values according to the configured number
of delay cycles. All storage locations are initialized to zero. The binary input CLR can be used
to set the output value y and all storage locations n to zero.
Parameter
Filter
Symbol
Function
The Filter component type maps the average over time of the X input to output Y.
Arithmetic mean
The arithmetic mean is calculated by adding up the time values of the input Xn and dividing it
by the number of cycles n.
Q
;Q ;Q ;Q
Q
< Q ;Q
L
L
Q
Median
All time values of the input Xn are put in (ascending) order by value. The median is the value
exactly in the middle.
[ Q QXQJHUDGH
<
Q Q
[ [ Q JHUDGH
Geometric mean
The geometric mean is the nth root of the product of all times values of the input X.
Q
; ;Q ;Q ;QQ
Q Q
< Q L Q
L
If the product is negative, the error message "Filter – geometric mean: the product Xi is
negative" (message category: ERROR) is generated and output Y is set to "0".
Parameter
INT – Integration
Symbol
Function
The INT component type forms the integral with the time-specific analog input signal x:
\ [ GW
7
The integral value y is limited to an interval defined by the two limits UL (high limit) and LL (low
limit):
LL ≤ y ≤ UL.
The binary outputs ULR and LLR indicate that the integral value has reached the low or high
limit:
LI \ ุ 8/
8/5
RWKHUZLVH
and
LI \ ื //
//5
RWKHUZLVH
The low limit must be less than the high limit. If this condition is violated, the error message “INT:
limits do not match" (message category ERROR) is generated and output y is set to 0.
The time constant T for the integration must have a positive value. If T is not positive, the error
message "INT: zero or negative time constant" (message category ERROR) is generated and
output y is set to zero.
The default setting is 0 for the low limit and 100 for the high limit. The default setting for the time
constant T is 1 s. All other inputs are set to 0 by default.
The integration value y can be set to the value at input SP over the binary input SET: if SET is
set to one, the integration value y is set to the value at the SP input. In this case too, the
integration value is limited by LL and UL.
Parameter
Operating window
The operating window shows the current function value as a percentage.
You can change the following values:
● Input value X even during the simulation
● Setpoint SP. Confirm the value with SET.
When the inputs SP, SET or X are connected to other components with signal lines, you must
first enable the respective signal isolator for manual operation.
Symbol
Function
The Interval component type checks whether an input value x is within the closed interval
[xmin, xmax]. If the input value is within the specified interval, the binary output is set to one;
otherwise, it is set to zero:
Parameter
The high interval limit may not be less than the lower interval limit. If the high interval limit
becomes less than the low limit during the simulation, the error message "Interval_I: limits do
not match" (message category ERROR) is generated and output b is set to zero.
Limiter
Symbol
Function
The Limiter component type maps an input value limited to the range from xmin to xmax onto the
output y:
The binary outputs bmin and bmax are set to one when the limiter takes effect, which means
Parameter
The high limit must not be less than the low limit. If the low limit is equal to or greater than the
high limit when simulation is run, the error message "Limiter: limits do not match" (message
category ERROR) is generated and output y is set to zero.
Symbol
Function
The component type MinMax maps the minimum or maximum of the n inputs X1 to Xn to
output y. The number of inputs n is variable and can be set to any value between 2 and 32. The
default value of all inputs is 0.
The MIN or MAX mapping set is displayed in the component symbol as shown in the figure
below:
Parameter
Multiplexer
Symbol
Function
The component type Multiplexer interconnects one of the n inputs xi to output in y in line with the
value at the integer selection input i:
y = xi for 1 ≤ i ≤ n.
The number n of inputs xi is variable and can be set to a value of between 2 and 32. The default
value of all inputs is "0".
The value at the selection input i is limited internally to 1 through n, which means that i is set
to "1" or values less than 1 and i is set to n for values greater than n. In the default setting, the
first input xi is therefore interconnected with the output y.
Symbol
Function
The component type PTn provides an nth order delay.
With a first order delay, the function value y at the output follows the value x at the input with a
delay equal to the differential equation:
G\
[ \
GW 7
A step change in the input value x from 0 to 1 therefore results in an exponential curve for the
output value y (step response):
y = 1 − e−t/T
as illustrated in the figure below.
For higher-order delays, the output value y is obtained by concatenating first-order delays:
G] L
]L ]L L Q
GW 7
y = zn
Where zi, i = 1,...n, are the n states of the nth order delay. To illustrate, an nth order delay
corresponds to n first order delays connected in series.
To prevent the component behaving in an unstable manner for delay times that are too short,
the delay time constant T is limited to values that are greater than or equal to the cycle time of
the component. If the values at input T are less than the cycle time, the error message "PTn:
delay time below cycle time“ (message category ERROR) is generated. The default delay time
is 1 s. All other inputs of the component are set to 0 by default.
The binary input SET may be used to set the output value y and the state values zi, i = 1,...n, to
the value at the input SP: If SET is set to 1, these values are set to the value at the input SP.
Parameter
Symbol
Function
The component type Ramp increments or decrements its function value y in each increment of
the simulation by the value
˂W
ෙ\ 8/ //
7
where Δt is the simulation increment width. The ramp value y is incremented by Δy when the
"+" (UP) input has the value 1. If the "–" input DOWN has the value 1, the ramp value y is
decremented by Δy. If both the "+" and the "–" input are set to 1, the ramp value y does not
change.
The ramp value is limited to an interval defined by the two limits UL (high limit) and LL (low limit):
LL ≤ y ≤ UL.
The binary outputs ULR and LLR indicate that the ramp value has reached the low or high limit:
LI \ ุ 8/
8/5
RWKHUZLVH
and
LI \ ื //
//5
RWKHUZLVH
The low limit must be less than the high limit. If this condition is violated, the error message
"RAMP: limits do not match" (message category ERROR) is generated and output y is set to 0.
The time constant T must have a positive value. If T is not positive, the error message "Ramp:
zero or negative time constant" (message category ERROR) is generated and output y is set
to 0.
The default low limit is 0 and the default high limit 100. The time constant is set to 10 seconds
by default. All other inputs are set to 0 by default.
The binary input SET can be used to set the ramp value y to the value at the SP input: If SET is
set to 1, the ramp value y is set to the value at the input SP. Here too, the ramp value is limited by
LL and UL.
Parameter
Operating window
The operating window shows the current function value as a percentage.
You can change the following values:
● Ramp function value over "Down" and "Up" buttons even during simulation
● Setpoint SP. Confirm the value with SET.
When the inputs SP, SET, "Down" or "Up" are connected to other components with signal lines,
you must first enable the respective signal isolator for manual operation.
Symbol
Function
The component type Selection interconnects one of the two inputs x0 and x1 to output y in line
with the value of the binary input a.
If the selection input a = 0, input x0 is interconnected; if the selection input a = 1, input x1 is
interconnected:
[ LI D
\
[ LI D
The default value of all inputs is 0.
Tracking
Symbol
Function
The component type Tracking tracks the outputs value Y to input value X with an adjustable
gradient. You can set the positive gradient (G_up) and negative gradient (G_down) separately.
The unit of the gradients is 1/second. If the Y output corresponds to the X input, the Y output
value remains constant.
The binary input SET can be used to set the output value Yto the value at the SP input. If SET
is set to True, the output value Y is set to the value at the input SP.
Parameter
Symbol
Function
The component type Weighted Average maps the weighted arithmetic mean of the analog
inputs X1, X2, X3 and X4 at output Y with the weightings W1, W2, W3 and W4.
; : ; : ; : ; :
<
: : : :
The sum of W1, W2, W3 and W4 must not be "0". If the sum is equal to "0" when simulation is run,
the error message "Weighted_Average:sum of W1, W2, W3 and W4 is zero – division by zero"
(message categoryERROR) is generated and output Y is set to "0".
The default setting for inputs X1, X2, X3, X4, W3 and W4 is "0". The default setting for inputs W1
and W2 is 1.0.
ADD_I – Addition
Symbol
Function
The ADD_I component type maps the sum of the analog values at the n inputs x1 to xn onto the
output y:
Q
\ [ L [ [ [Q
L
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to zero by default.
SUB_I – Subtraction
Symbol
Function
The SUB_I component type maps the difference between the integer values at the two inputs x1
and x2 onto the output y according to
y = x1 − x2
All inputs are set to zero by default.
MUL_I – Multiplication
Symbol
Function
The MUL_I component type maps the product of the integer values at the n inputs x1 to xn onto
the output y:
Q
\ [
L
L [[[Q
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to one by default.
Symbol
Function
The DIV_I component type maps the quotients of the integral values at the inputs x1 and x2
according to
x1 = y · x2 + R
integer division with remainder. The integer quotient of the division is output at the y output and
the remainder of the integer division at the R output.
The divider at input x1 is set to zero by default, while the divisor input x2 is set to one by default.
The value of the divisor x2 must not be zero. If the devisor becomes zero during the simulation,
the error message "DIV_I: division by zero“ (message category ERROR) is generated and
output y and the remainder R are set to zero.
Symbol
Function
The component type Compare_I compares the integer inputs x1 and x2. The binary output b is
set to 1 if the relational expression is true. Otherwise, b is set to 0.
The selected comparison operator is displayed in the component symbol. To inset the relational
operators "<=", ">=" and "<>" from the right of the symbol, change the width of the symbol.
Parameters
LI [ [
E
RWKHUZLVH
● Less than or equal to comparison
(<=), which means
LI [ ื [
E
RWKHUZLVH
● Greater than comparison (>), which
means
LI [ ! [
E
RWKHUZLVH
● "Greater than or equal to"
comparison (>=), which means
LI [ ุ [
E
RWKHUZLVH
● Equal to comparison (=), which
means
LI [ [
E
RWKHUZLVH
● Not equal to comparison (<>), which
means
LI [ ำ [
E
RWKHUZLVH
Symbol
Function
The Interval_I component type checks whether an integer input value x is within the closed
interval [xmin, xmax]. If the input value falls within the set interval, the binary output is set to one;
otherwise it is zero:
Limiter_I – Limiter
Symbol
Function
The Limiter_I component type maps an input value limited to the range from xmin to xmax onto the
output y:
The binary outputs bmin and bmax are set to one when the limiter takes effect, which means
Symbol
Function
The component type MinMax_I maps the minimum or maximum of the n inputs z1 to zn to
output y. The number of inputs n is variable and can be set to any value between 2 and 32. The
default value of all inputs is 0.
The MIN or MAX mapping set is displayed in the component symbol as shown in the figure
below:
Parameter
Symbol
Function
The component type Multiplexer_I interconnects one of the n different Integer inputs xi to output
in y in line with the value at the integer selection input i:
y = xi for 1 ≤ i ≤ n.
The number n of inputs xi is variable and can be set to a value of between 2 and 32. The default
value of all inputs is 0.
The value at the selection input i is limited internally to 1 through n, which means that i is set
to 1 or values less than 1 and i is set to n for values greater than n. In the default setting, the first
input xi is therefore interconnected with the output y.
Symbol
Function
The component type Selection_I interconnects one of the two integer inputs x0 and x1 to
output y in line with the value of the binary input a.
If the selection input a = 0, input x0 is interconnected; if the selection input a = 1, input x1 is
interconnected:
[ LI D
\
[ LI D
The default value of all inputs is 0.
Note
You can also use the AFormula component with suitable parameters instead of these
components.
You can increase the available mathematical functions of this type by creating suitable
component types using the SIMIT Component Type Editor (CTE) expansion module.
Symbol
Function
The ABS component type maps the absolute value of input x onto output y:
y = |x|.
Symbol
The symbol for ABS_I is blue to distinguish it from the ABS component type.
Function
The ABS_I component type maps the absolute value of integer input x onto integer output y:
y = |x|.
Symbol
Function
The component type COS maps the cosine of input x to output y:
y = cos(x).
Parameter
Symbol
Function
The EXP component type maps the exponential value of input x onto output y:
y = ex
LN – Natural logarithm
Symbol
Function
The LN component type maps the natural logarithm of input x onto output y:
y = ln(x).
The argument x must be positive. If the argument becomes less than or equal to zero during the
simulation, the error message "LN: invalid argument" (message category ERROR) is
generated and output y is set to zero. The argument x is set to one by default.
Symbol
Function
The LOG component type maps the common logarithm of the X input to output Y.
Y = Log10X
Argument X must be positive. If the argument is less than or equal to "0" when simulation is run,
the error message "LOG: invalid argument" (message category ERROR) is generated and
output Y is set to "0". The default setting for input X is 1.0.
POW – Power
Symbol
Function
The POW component type maps the base (input) X to the power (input) P to output Y.
Y=X P
Symbol
Function
The component type RAND returns randomly generated numbers at its output Y, the ranges
and distribution of which are set with parameter Distribution.
Note
Note that the random numbers are calculated and therefore are not unpredictable.
Parameter
Symbol
Function
The component type SIN maps the sine of input x to output y:
y = sin(x).
Parameter
Symbol
Function
The SQRT component type maps the square root of input x onto output y:
\ [
The radicand x must not be negative. If the radicand becomes negative during the simulation,
the error message "SQRT: invalid argument" (message category ERROR) is generated and
output y is set to zero.
Symbol
Function
The component type TAN maps the tangent of input x to output y:
y = tan(x).
Parameter
AND – Conjunction
Symbol
Function
The AND component type maps the n binary values at the inputs ai as a conjunction, which
means using a logical (Boolean) "AND" function, onto the output b:
Q
E ID L
L
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to one by default.
OR – Disjunction
Symbol
Function
The OR component type maps the n binary values at the inputs ai as a disjunction, which means
using a logical (Boolean) "OR" function, onto the output b:
Q
E UD L
L
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to zero by default.
Symbol
Function
Output b is equal to the negated input a, which means
E D
As can be seen in the figure below, when the NOTc component type is used, the negation can
be applied clearly and compactly to the inputs or outputs of components.
XOR – Non-equivalence
Symbol
Function
The XOR component type maps the n binary values at the inputs ai onto the output b using the
"Exclusive-OR" function: b is one, if an odd number of inputs ai is one. In all other cases b is zero.
For two inputs
b = a1 ⊗ a2
which is the non-equivalence or "unequal" function.
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to zero by default.
XNOR – Equivalence
Symbol
Function
The XNOR component type maps the n binary values at the inputs ai onto the output b using the
"Exclusive NOR" function: b is one, if an even number of inputs ai is one. In all other cases b is
zero.
For two inputs
E D D
which is the equivalence or "equal" function.
The number of inputs n is variable and can be set to any value between 2 and 32. All inputs are
set to zero by default.
Symbol
Function
The component type BFormula allows the use of explicit logical expressions. This logic
function f calculates a value in relation to the n values at the inputs ai. The function value is
assigned to the output b:
b = f(a1,...,an)
The number n of inputs can be varied between 1 and 32. Only the inputs that are available
according to the number currently set may be used in the formula.
The operators listed in the following table may be used in formulas.
Operator Function
AND Conjunction (AND function)
OR Disjunction (OR function)
NOT Negation
( Opening parenthesis
) Closing parenthesis
Note
There is no check in the formula component to determine whether all the set inputs are used in
the specified formula.
Parameter
You can make the component wider to allow longer formulas to be displayed in full.
Symbol
Function
The component type Counter allows you to count the change in binary signals. When the binary
value at the "+" input changes from zero to one, the counter value is incremented at output y.
When the binary value at the "–" input changes from zero to one, the counter value is
decremented at the y output.
The counter value is limited to an interval defined by the two limits UL (high limit) and LL (low
limit):
LL ≤ y ≤ UL.
The binary outputs ULR and LLR indicate when the counter value has reached the low or high
limit:
LI \ ุ 8/
8/5
RWKHUZLVH
and
LI \ ื //
//5
RWKHUZLVH
The low limit must be less than the high limit. If this condition is violated, the error message
"Counter: limits do not match" (message category ERROR) is generated and the counter value
at output y is set to zero.
The binary input SET may be used to set the counter value y to the value at the input SP: If SET
is set to one, the counter value y is set equal to the value at the input SP. Here, too, the counter
value is limited by LL and UL.
The limits are set to zero for the low limit and to one hundred for the high limit by default. All other
inputs are set to zero by default.
Parameter
Symbol
Function
With the component type Delay, the binary signal b at the output is tracked to the binary signal a
at the input with a delay.
If the signal at the input changes from zero to one, the output is set to one once the ON-delay
time TON has elapsed. If the input signal is reset to zero before the ON-delay time has elapsed,
the output signal remains unchanged at zero. If the signal at the input changes from one to zero,
the output is set to zero once the OFF-delay time TOFF has elapsed. If the output signal is reset
to one before the OFF-delay time has elapsed, the output signal remains unchanged at one.
This interaction is illustrated in the table below.
Table 8-4 Signal curves at the input and output of the Delay component
Input a
Output b
The delay times must not assume a negative value. If a delay time assumes a negative value,
the error message "Delay: on-delay time negative value" or "Delay: off-delay time negative
value" (message category ERROR) is generated and the corresponding delay time is set to
zero.
Symbol
Function
The component type Multiplexer_B interconnects one of the n inputs Xi to output Y in line with
the value at the integer selection input SEL:
Y = Xi for 1≤ i ≤ n
The number n of inputs Xi is variable and can be set to a value of between 2 and 32. The default
value of all inputs is False.
The value at the selection input SEL is limited internally to 1 through n. i is set to 1 for values
less than 1 and SEL is set to n for values greater than n. In the default setting, the first input X1
is interconnected with output Y.
Pulse – Pulse
Symbol
Function
The component type Pulse sets output b if there is an edge change from 0 to 1 at input a. The
output b is reset once the time T has elapsed. A pulse with pulse width T is thus generated at
output b. The pulse width can be set via the signal at analog input T.
Table 8-5 Signal curves at the input and output of the Pulse component
Input a
Output b
The pulse width T must not be negative, or the error message "Pulse: pulse width negative
value" (message category ERROR) is generated and output b is set to 0. For pulse widths that
are smaller than the simulation cycle time, the output pulse is set to the duration of one
simulation cycle.
Parameter
Symbol
Function
The component type RS_FF provides the simplest type of flip-flop: an RS flip-flop. If the value
at the set input S is equal to one, the output value Q is set to one. If the input value at the reset
input R1 is set to one, the output is reset to zero. The reset input is dominant, which means if
both inputs are set to one, output Q is reset to zero. The output 4 always assumes the inverse
value of output Q.
The table below lists the possible states of the RS_FF component type.
Parameter
Symbol
Function
The component type Selection_B interconnects one of the two binary inputs X0 and X1 to output
Y in line with the value of the binary input SEL.
If selection input SEL = False, input X0 is interconnected; if selection input SEL = True, input X1
is interconnected.
; LI 6(/ IDOVH
<
; LI 6(/ WUXH
The default value of all inputs is False.
Symbol
Function
The component type SR_FF maps an SR flip-flop. If the value at the set input S1 is equal to one,
the output value Q is set to one. If the input value at the reset input R is set to one, the output
is reset to zero. The set input is dominant, which means if both inputs are set to one, output Q is
reset to one. The output 4 always has the inverse value of output Q.
The table below lists the possible states of the component SR_FF .
Parameter
Symbol
Function
The Bit2Byte component type converts the binary input values bi , i = 0, ..., 7, into a byte value B
at the integer output according to
% E ຘ
L
L
L
In the conversion, b0 therefore represents the least significant bit and b7 the most significant bit.
The individual bits bi may be set individually while the simulation is running in the component
operating window. To set a bit, open the component operating window. Then select the bits that
you wish to set manually by pressing the button to the left of those bits. You can then set and
reset each bit by pressing the button on the right, which means toggle between zero and one.
In the figure below, bits b0, b3 and b7 are selected to be set and bit b3 is set.
Unset bits are identified by a light blue border, while set bits have a dark blue border.
Symbol
Function
The Byte2Bit component type converts a byte value at the integer input B into binary values bi , i
= 0, ... ,7 at the outputs. In the conversion, b0 will be the least significant bit and b7 the most
significant bit of the byte value.
The input is limited to the range of values of one byte, which means to the range from zero to
255. If the input value is not within this range during the simulation, the message "Byte2Bit:
input not a valid byte value" (message category ERROR) is generated.
The individual output bits bi may be set individually while the simulation is running in the
component operating window. To set a bit, open the component operating window. Then select
the bits that you wish to set manually by pressing the button to the left of those bits. You can
then set and reset each bit by pressing the button on the right, which means toggle between
zero and one. In the figure below, bits b0, b4 and b6 are selected to be set and bit b4 is set:
Symbol
Function
The Byte2Word component type combines two byte values B1, B0 at the integer inputs to form
a word at the integer output W. B1 is the most significant byte and B0 is the least significant byte.
The values at the input are limited to the range of values of one byte, which means to the range
from zero to 255. If an input value is not within this range during the simulation, the message
"Byte2Word: input not a valid byte value" (message category ERROR) is generated.
Symbol
Function
The Word2Byte component type breaks down a word at the integer input W into two byte
values B1, B0 at the integer outputs. B1 is the most significant byte and B0 is the least significant
byte.
The value at the input is limited to the range of values of one word, which means to the range
from zero to 216–1. If the input value is not within this range during the simulation, the message
"Word2Byte: input not a valid word value" (message category ERROR) is generated.
Symbol
Function
The Byte2DWord component type combines four byte values Bi, i = 0, ... ,3, at the integer inputs
to form a double word in the order B3 – B2 – B1 – B0 at the integer output DW. B3 is therefore the
most significant byte and B0 is the least significant byte.
The values at the input are limited to the range of values of one byte, which means to the range
from zero to 255. If an input value is not within this range during the simulation, the message
"Byte2DWord: input not a valid byte value" (message category ERROR) is generated.
Symbol
Function
The DWord2Byte component type converts a double word at the integer input DW into four
binary values Bi, i = 0, ... ,3 at the integer outputs. B3 is the most significant byte and B0 is the
least significant byte.
The value at the input is limited to the range of values of one double word, which means to the
range from zero to 232–1 . If the input value is not within this range during the simulation, the
message "DWord2Byte: input not a valid double word value" (message category ERROR) is
generated.
Symbol
Function
The Integer2Analog component type converts an integer value at the input into an analog value
at the output.
Symbol
Function
The Analog2Integer component type converts an analog value at the input into an integer value
at the output. The integer value is rounded.
Symbol
Function
The component type Raw2Phys converts an integer x at the input to an analog output value y
in accordance with simple linear transformation:
\ \/ \8 \/
[ [/ [8 [/
The input value x may be a so-called raw value from an automation system, for example. The
output value y is then the value mapped within a defined physical range of values.
Parameter
You can change the parameters during the course of the simulation.
Symbol
Function
The component type Phys2Raw converts an analog value x at the input to an integer output
value y in accordance with simple linear transformation:
[ [/ [ 8 [/
\ \/ \8 \/
The input value x is thus transformed as a measurement of a physical value into the raw value y
for an automation system, for example.
Parameter
You can change the parameters during the course of the simulation.
Symbol
Function
The Unsigned2Signed component type converts an unsigned integer value x at the input to a
signed value y at the output.
The parameter Width determines which data width is assigned to the input value: 1 byte, 2 bytes
or 4 bytes. The output value is limited in accordance with the set data width. The conversion is
done as follows:
Data width: 1 byte
LI [ !
LI [
\
[ [ !
LI
[ RWKHUZLVH
Data width: 2 bytes
LI [ !
LI [
\
[ [ !
LI
[ RWKHUZLVH
LI [ !
LI [
\
[ [ !
LI
[ RWKHUZLVH
Symbol
Function
The Signed2Unsigned component type converts a signed integer value x at the input to an
unsigned value y at the output.
The parameter Width determines which data width is assigned to the output value: 1 byte, 2
bytes or 4 bytes. The output value is limited in accordance with the set data width. The
conversion is done as follows:
Data width: 1 byte
LI [
LI [ !
\
[ [
LI
[ RWKHUZLVH
Data width: 2 bytes
LI [
LI [ !
\
[ [
LI
[ RWKHUZLVH
Data width: 4 bytes
LI [
LI [ !
\
[ [
LI
[ RWKHUZLVH
Symbol
Function
The component type Real2Byte converts the values of an analog signal at the REAL input to
the binary representation of an single-precision floating-point number ("single" type) in
accordance with IEEE 754. The converted floating-point number is mapped to the four byte
values Bi, i = 0, ... ,3, at the integer outputs as illustrated in the figure below.
V Sign
E Exponent
M Mantissa
Note
Mapping the analog signal (type double) to the single precision number format (type single)
limits the precision and the value range.
This conversion cannot be used to convert a floating-point number to a whole number (integer).
The Analog2Integer component type should be used for this conversion.
If you want to transfer analog signals to a SIMATIC controller, you normally set the data type
of the corresponding signal in the coupling to REAL. The analog signal is then converted
automatically. A component of the Real2Byte type is necessary, however, if you want to
transfer analog signals directly to bit memories or data blocks of a SIMATIC controller, for
example.
Symbol
Function
The Byte2Real component type converts the binary representation of a floating-point number
of type "single" as defined in IEEE 754 at the integer inputs Bi, i = 0, ... ,3 to the value of an
analog signal at the REAL output as shown in the figure below.
V Sign
E Exponent
M Mantissa
Note
This conversion cannot be used to convert a a whole number (integer) into a floating-point
number. The Analog2Integer component type should be used for this conversion.
If you want to receive floating-point numbers from a SIMATIC controller, you normally set the
data type of the corresponding signal in the coupling to REAL. The conversion to an analog
signal then takes place automatically. A component of the Byte2Real type is necessary,
however, if you want to transfer floating-point numbers directly from bit memories or data blocks
of a SIMATIC controller, for example.
Connectors
Three connector component types – referred to simply as connectors – are available:
● The analog connector component type AConnector,
● the binary connector component type BConnector and
● the integer connector component type IConnector.
Connector components
Analog connector
Binary connector
Integer connector
A connector component transfers the input value to its output without change or delay. They are
used, for example, in the following cases:
● Connectors (I/O connectors or global connectors) cannot be connected directly to each
other. As shown in the example in the figure below, connectors can be connected with the
aid of connector components.
● An input element, for example a converter, is linked directly to the signal to be set. With the
aid of a connector, the input element can influence several components directly. As shown
in the example in the figure below, the input signal IN of the connector VB is linked to the
input element.
● Component inputs can be directly assigned a default value. With the aid of a connector,
several inputs can be assigned a single default value. As shown in the example in the figure
below, a connector is connected to the inputs of the components to be set. The value to be
set is then set at the input of the connector.
Analog constant
Binary constant
Integer constant
Parameters of a macro component can only be built from parameters of the components that
are used within the macro component. The constant component types thus also provide a
parameter for setting inputs of a component as a macro parameter.
You can find additional information on this in the section: Defining parameters of macro
components (Page 239)
Symbol
Function
The following integer values are available at the outputs of a component of this type:
● ProjectVersion
The complete version number coded in numerical form.
● LicenseNumber
The license number coded in numerical form.
● TimeStamp
The time stamp
● MajorVersion
The major version
● MinorVersion
The minor version
Operating window
The individual version numbers are displayed in readable form in the component operating
window.
SimulationLoad
Symbol
Function
The SimulationLoad component type shows the current simulation load. You can find
information about the simulation load in the section: Display of the simulation load (Page 39).
The symbol shows the total load in % under "Total". All values in this component are not limited
and not smoothed. The values may therefore fluctuate more than the value in the symbol for the
simulation in progress.
The three binary displays OK, Critical and Overload return a rough assessment of the load
value as follows:
Operating window
This component shows the load values for all eight time slices in the operating window. The
following causes are distinguished:
● Components (Components)
● Solution procedures (Solvers)
● Couplings (Gateways)
SIMIT distinguishes between Time and CPU-Ticks.
Time
Time is the percentage ratio of actual cycle time to configured cycle time.
The model with the worst time value is closest to the overload limit. However, this does not
necessarily mean that there is too much calculation in this time slice.
The computational load is distributed across multiple available cores. Usually, a computing
core must work through more than one time slice. Time slices with shorter cycle times have a
higher priority. This means that the calculation of a slower time slice may be interrupted to
permit the calculation of a faster time slice. This is important to calculate all cycles within the
configured cycle time, if possible.
The result can be that the calculation in a slow time slice is constantly being interrupted by the
calculation of a faster time slice, thereby creating a load problem. The faster time slice, in
contrast, is calculated with a higher priority and can therefore have a lower load.
CPU-Ticks
To better identify the real cause of a high simulation load, CPU-Ticks are also available. They
do not indicate the time that was needed for the calculation, but rather a measure for the time
spent on the calculation operations. They do not take into account wait times due to
interruptions by other time slices. As the measured absolute value of CPU-Ticks is not very
meaningful, it is scaled:
0$;Q
0RGHOWLPHQ 6ROYHUWLPH
Q
0RGHO7LFNV
L 0RGHO7LFNVL
0$;Q
0RGHOWLFNVQ 6ROYHUWLFNV
Q
0$;Q
0RGHOWLPHQ 6ROYHUWLPH
Q
6ROYHU7LFNV
L 6ROYHU7LFNVL
0$;Q
0RGHOWLFNVQ 6ROYHUWLFNV
Q
ModelTicksn’: Displayed value for the computational load of the component code in time slice n
SolverTicksn’: Displayed value for the computational load of the solution procedure in time slice
n
ModelTicksn: Measured value for the computational operations of the component code in time
slice n
SolverTicksn: Measured value for the computational operations of the solution procedure in
time slice n
ModelTimen: Ratio of the time required for the calculation of the component code to the
configured cycle time in time slice n
SolverTimen: Ratio of the time required for the calculation of the solution procedure to the
configured cycle time in time slice n
The ratio of tick values to each other shows where most arithmetic operations are performed in
a given time. Relief should be provided in the time slice with the highest values, for example by
relocating parts of the simulation model to a slower time slice or setting the entire critical time
slice to a slower speed.
Simulation load by couplings
When calculating the tick values, it is assumed that the components and solution procedures
only perform calculations and do not perform any file or console tasks. Although these
commands require time, they do not fully utilize the calculation cores and therefore lead to
misleading information.
Therefore, the couplings are not included in the count of arithmetic instructions. If a high
simulation load is caused by a coupling, there are two reasons for this:
● The coupling is being interrupted too often by higher priority calculations.
● The coupling itself demands a great deal of time.
In the second case, reducing the computational work in the area of components or solution
procedure is not very helpful. In general, the coupling must be assigned to a slower time slice,
the signal range of the coupling must be reduced, or a part of the signals must be relocated to
a second coupling with a slower cycle time.
Output signals
The SimulationLoad component has output signals for operating controls in the operating
window. These signals cannot be interconnected to the component symbol, but can be
monitored in the property view.
Link
The average load X over time is shown at the component link on the Load digital display.
Q
;Q ;Q ;Q
Q
$Q]HLJH /RDG ;Q
Q L
Q
L
The number of total steps n is counted. The number of increments at which "TRUE" is pending
at binary signal OK is counted internally (nok).
The digital display OK shows the percentage of increments in which the load was in the OK
range.
QRN
$Q]HLJH 2.
Q
The number of increments at which "TRUE" is pending at binary signal Critical is counted
internally (ncritical).
The digital display Critical shows the percentage of increments in which the load was in the
Critical range.
Q&ULWLFDO
$Q]HLJH &ULWLFDO
Q
The number of increments at which "TRUE" is pending at binary signal Overload is counted
internally (noverload).
The digital display Overload shows the percentage of increments in which the load was in the
Overload range.
Q2YHUORDG
$Q]HLJH 2YHUORDG
Q
The Reset button restarts the calculation. The values of the previous increments are
disregarded from this point and all counters are reset.
Symbol
Function
The component type SimulationTime returns the current simulation time at its four outputs. The
output takes place at the Time output as an integer value in milliseconds. The simulation time
is available at the H, M and S integer outputs, broken down into hours (H), minutes (M) and
seconds (S).
The simulation time is the time that is counted in the simulation cycle when simulation is
performed. The simulation time is set to zero when a simulation is initialized or started. The
simulation time and real time run synchronously if the simulation is running in real-time mode.
In slow-motion simulation mode, the simulation time is slower than real time; in quick-motion
simulation mode, the simulation time is faster than real time. If the simulation is paused, the
simulation time is stopped as well. When the simulation is resumed, the simulation time starts
running again as well.
Operating window
The operating window shows the simulation time. You can reset the simulation time
with Reset.
Symbol
Function
The WaveformGenerator component type generates periodic signals at output Y. Input Run
must be set to True for output Y to be calculated dynamically. If Run has the value False, the
Y value last calculated remains.
The Period input is specified in seconds; Amplitude is an absolute numerical value. The
significance of these two inputs differs depending on the Waveform setting.
The SquareRate input is only active with the Square setting and sets the percentage ratio of
Tlow to Thigh.
Square
Triangle
Sine
Sawtooth
Parameter
Four component types are available (DriveV1, DriveV2, DriveV3 and DriveV4) to simulate
valve drives. All four of these component types share the outputs and some of the inputs as
illustrated in the figure below.
The two analog inputs TOpen and TClose indicate the opening and closing times of the drive,
which means the time that the drive takes to fully open or close. If one of the two input values
is negative during simulation, the message "DriveVx: closing or opening time invalid value"
(message category ERROR) is generated.
The current position value of the drive is output at analog output Y as a percentage, which
means in the range from zero to one hundred:
0 ≤ Y ≤ 100.
The value zero corresponds to the fully closed valve, while the value one hundred represents
the fully open valve.
The four binary outputs 100, Hi, Lo and 0 may be interpreted as limit switches for the drive:
● 100 and 0 as limit switches "Valve fully opened" or "Valve fully closed",
● Hi and Lo as pre-limit switches for "Valve open" or "Valve closed".
The limit switches are permanently set to the position values zero (for the fully closed valve) and
one hundred (for the fully open valve). Binary outputs 100 or 0 are therefore set to one when the
valve is fully closed or open, which means when the position Y of the component has the value
zero or one hundred.
The Hi and Lo pre-limit switches can be set using the HI_Limit or LO_Limit parameters. Their
values are between 0 and 100. Position values of five (LO_Limit) and 95 (HI_Limit) are set by
default.
If one of the two parameter values is negative during the simulation, the message "DriveVx:
high and low parameters do not match" (message category ERROR) is generated.
The Initial_Value parameter is used to set the valve drive to the starting position of Closed or
Open. The default setting for Initial_Value is Closed.
The current position value of the drive is visualized as a bar graph display in the component
operating window. The button on the left labelled MANUAL is used to change the position value
to the desired setting by moving the slider in the operating window.
The position value is then no longer derived from the component inputs, but rather tracks the
value set using the slider. The set opening and closing times remain active. The four binary
outputs 100, Hi, Lo and 0 likewise all remain effective. They are also set as described above if
the position value is to be tracked.
Symbol
Function
The DriveV1 component type simulates a drive unit that sets the position value Y at the output
in relation to a binary value at the input Open. If the binary input is equal to zero, the position
value Y is continuously tracked to zero with the closing time TClose. If the binary input is equal to
one, the position value is continuously tracked to one hundred with the opening time TOpen. The
position value thus only has the two steady states of zero and one hundred, which means the
states "Valve open” and “Valve closed” in relation to the valve function. The drive or the valve
is thus opened or closed whenever the binary value at the input changes.
Symbol
Function
The DriveV2 component type simulates a drive unit that sets the position value Y at the output
in relation to two binary values at the Open and Close inputs. If the binary value at input Open
is equal to one, the position value Y is continuously tracked to one hundred with the opening
time TOpen. If the binary value at the input Close is equal to one, the position value is continuously
tracked to zero with the closing time TClose.
If both input values are set to one or zero at the same time, the position value remains
unchanged. The position value thus only changes if the binary value at either the Open input or
the Close input is set to one.
Symbol
Function
The DriveV3 component type simulates a drive unit that sets the position value Y at the output
in relation to three binary values at the Open, Close and Stop inputs. If the binary value at
the Open input changes from zero to one, the position value Y is continuously tracked to one
hundred with the opening time TOpen. The position value is tracked continuously to zero with the
closing time TClose if the binary value at the Close input changes from zero to one. If the binary
value at the Stop input changes from zero to one, the position value remains unchanged.
Opening, closing and stopping of the drive is thus initiated via the edge of the corresponding
binary input signal (signal change from zero to one).
Symbol
Function
The DriveV4 component type simulates a drive unit that sets the position value Y at the output
that continuously tracks the analog value at the Value input. The tracking occurs in the direction
of rising position values with the opening time TOpen and falling position values with the closing
time TClose. The position value is always limited to values from zero to one hundred, even if the
input value is outside this interval.
The two component types DriveP1 and DriveP2 may be used in the simulation as drives for
pumps, fans or similar units. The outputs and some of the inputs common to these two
component types are illustrated in the figure below:
The run-up and run-down speeds of the drive are set at the two analog inputs TUp and TDown. TUp
is the time it takes the drive to run up from standstill to the nominal speed in seconds, while TDown
is the time in seconds it takes to run the drive down from nominal speed to standstill. Both times
have a default value of one second. If one of the two input values is negative during simulation,
the message "DriveVx: run-up or run-down time invalid value" (message category ERROR) is
generated.
The current speed value of the drive is output at analog output Y as a percentage, which means
in the range from zero to one hundred:
0 ≤ Y ≤ 100.
The value zero corresponds to the stopped drive, while the value one hundred represents the
drive at nominal speed.
The direction of rotation of the drive can be set using binary input Dir. When this input is set to
zero, the direction of rotation is positive. If the input is set to one, the direction of rotation is
negative. This input can therefore be used to specify whether the drive turns clockwise or
counterclockwise, for example. If it turns in the negative direction, the speed is output as a
negative value at output Y:
−100 ≤ Y ≤ 0.
Positive values for Y thus indicate speeds in the positive direction, while negative values
indicate speeds in the negative direction. The change in direction of rotation only takes effect
if the drive is at a standstill.
The binary input Speed is used to toggle the speed between nominal speed (full speed) and
partial speed (low speed). If Speed is one, the nominal speed was selected; otherwise the
partial speed was selected. The default setting for the Speed binary input is one. The partial
speed is specified as a numerical value (percentage) at the analog input xLSp:
0 ≤ xLSp ≤ 100.
The default setting for the partial speed is 50, which means half the nominal speed. If the partial
speed is not within the defined range, the message "DrivePx: low speed invalid value"
(message category ERROR) is generated.
The binary output Run is only set to one when the drive has reached the preset speed value in
the positive or negative direction of rotation, which means only if the absolute value at the
analog output Y is equal to one hundred (nominal speed) or is equal to the partial speed set at
the input xLSp.
The feedback signal for the selected speed is available at the binary output Speed. The binary
output is only set to one if the drive has reached its nominal speed in the positive or negative
direction of rotation.
The value at the binary output Dir takes the form of a feedback signal for the current direction
of rotation of the drive. The binary output is zero if the drive is turning in the positive direction;
the value is one if the drive is turning in the negative direction.
The current speed value of the drive is visualized as a bar graph display in the component
operating window. The button on the left labelled MANUAL is used to change the speed value
to the desired setting by moving the slider in the operating window.
The speed value is then no longer derived from the component inputs, but rather tracks the
value set using the slider. The specified start-up and run-down times remain effective. The
binary outputs Run, Speed and Dir likewise remain active. They are also set as described
above if the speed value is to be tracked.
Symbol
Function
The DriveP1 component type simulates a drive unit that is switched on and off via the binary
value at the Run input. The drive is switched on while the input value is set to one. If the input
value is set to zero, the drive is switched off.
Symbol
Function
The DriveP2 component type simulates a drive unit that is switched on and off via the two binary
inputs Start and Stop. If the binary value Start changes from zero to one, then the drive is
switched on. If the binary value Stop changes from zero to one, the drive is switched off.
Activation and deactivation of the drive is initiated with the edge of the corresponding binary
input signal (signal change from zero to one).
8.1.4.4 Motor
Analog inputs
The start-up and run-down times of the drive are specified at the analog inputs T_UP
and T_DOWN.
T_UP is the time it takes the drive to run from standstill to the nominal speed in seconds;
T_DOWN is the time in seconds it takes to run the drive down from nominal speed to standstill.
The default time is 1 s.
If one of the two input values is negative during the simulation, the message "Motor: run-up or
run-down time invalid value" (message category ERROR) is generated.
Binary inputs
Binary input LocalAct switches the drive to the local operating mode. In this mode, the drive can
only be controlled over the component operating window. The drive can be locked with the
binary input LockAct so that neither local operation nor operation using the component control
inputs is possible. The drive is shut down and locked if the component receives a rising edge
at the LockAct input during operation.
Binary outputs
The binary output FbkOff is True when the drive is at a standstill (Y = 0). The binary output Local
can be activated from the drive operating window. If the output is connected accordingly, it can
send local operations to the controller. The binary output Maint can be activated from the drive
operating window. The binary output Trip can be activated from the drive operating window. If
Trip is enabled, the drive shuts down and remains at a standstill (Y =0).
Analog output
The current speed of the drive is output as a percentage at analog output Y, in other words in
a range of 0 to 100:
0 ≤ Y ≤ 100 or with ReversibleMotor −100 ≤ Y ≤ 100.
A value of 0 corresponds to a drive at a standstill and a value of 100 to a drive at the nominal
speed (or –100 with ReversibleMotor).
Motor
Symbol
Function
The component type Motor simulates a drive unit that is switched on and off by the binary value
at the Start input. The drive is on for as long as the start input value is set to True. If the start
input value is set to False, the drive is switched off.
The component can also be switched on and off with the two binary inputs P_Start and P_Stop .
If the binary signal at the P_Start input changes from False to True , the drive is switched on.
If the binary signal at the P_Stop input changes from False to True, the drive is switched off.
The speed value of the drive can be specified as a percentage in the range from 0 to 100 via
the analog input Setpoint. The default setting for the component is 100. If the speed value is not
in this defined range, the message "Motor: Setpoint invalid value" (message category ERROR)
is generated.
The binary output FbkRun is only set to True if the drive has reached the preselected speed in
a positive direction: The value at analog output Y is identical to the value specified at the
Setpoint input.
The binary outputs StartLocal and StopLocal only represent the duration of the key operation
to set the Start or Stop key in the component operating window to True.
Operating window
The component operating window shows the current speed of the drive as a bar graph.
The left-hand column shows the two inputs LocalAct and LockAct. You can see the current
state pending here.
You can also separate both inputs from their sources and set the value manually.
If LocalAct (Local active) is enabled, the speed is no longer derived from the inputs of the
component. Instead, it is formed from the local operating buttons in the central column Start and
Stop. The specified start-up and run-down times remain effective. The switch from remote to
local is smooth: If the drive was on before the switchover, it is initially also on immediately
afterwards.
In the right-hand column is the operating switch for Local, maintenance (Maint) and Trip.
Symbol
Function
The component type ReversibleMotor simulates a drive unit that is controlled by two binary
values at the Fwd and Rev inputs. The drive is switched on in forwards mode as long as the
input value Fwd is set to True. If the input value is set to False, the drive is switched off. The
drive is switched on in reverse mode for as long as the input valueRev is set to True. If the input
value is set to False, the drive is switched off.
The component can also be pulse-controlled over the three binary inputs P_Fwd, P_Rev and
P_Stop. If the binary signal at the P_Fwd input changes from False to True, the drive is switched
on in forwards mode. If the binary signal at the P_Stopinput changes from False to True, the
drive is switched off. If the binary signal at the P_Rev input changes from False to True , the
drive is switched on in reverse mode.
The change in direction of rotation only takes effect if the drive is at a standstill.
The speed value of the drive can be specified as a percentage in the range from 0 to 100 via
the analog input Setpoint. The default setting for the component is 100. If the speed value is not
in this defined range, the message "Motor: Setpoint invalid value" (message categoryERROR)
is generated.
The binary output FbkFwd is only set to True if the drive has reached the preselected speed in
a positive direction (forwards mode): The value at analog output Y is identical to the value
specified at the Setpoint input.
The binary output FbkRev is only set to True if the drive has reached the preselected speed in
a negative direction (reverse mode): The value at analog output Y is the negative of the value
specified at the Setpoint input.
The binary outputs FwdLocalRevLocal and StopLocal only represent the duration of the key
operation to set the Forward, Reverse or Stop key in the component operating window to True.
Operating window
The component operating window shows the current speed of the drive as a bar graph.
The left-hand column shows the two inputs LocalAct and LockAct. You can see the current
state pending here.
You can also separate both inputs from their sources and set the value manually.
If LocalAct (Local active) is enabled, the speed is no longer derived from the inputs of the
component. Instead, it is formed from the local operating buttons in the central column,
Forward, Reverse and Stop. The specified start-up and run-down times remain effective. The
switch from remote to local is smooth: If the drive was on before the switchover, it is initially also
on immediately afterwards.
In the right-hand column is the operating switch for Local, maintenance (Maint) and Trip.
Symbol
Function
The component type TwoSpeedMotor simulates a drive unit that is controlled by two binary
values at the Spd1 and Spd2 inputs. The drive is switched on and run until Setpoint1 as long
as the input value Spd1 is set to True. If the input value is set to False, the drive is switched off.
The drive is switched on and run until Setpoint2 as long as the input value Spd2 is set to True.
If the input value is set to False, the drive is switched off. If both the Spd1 and Spd2 input are
pending at the same time, the drive is operated at Spd1 .
The component can also be pulse-controlled over the three binary inputs P_Spd1, P_Spd2 and
P_Stop. If the binary signal at the P_Spd1 input changes from False to True, the drive is
switched on at the reduced percentage speed specified at the Setpoint1 input. If the binary
signal at the P_Stopinput changes from False to True, the drive is switched off. If the binary
signal at the P_Spd2 input changes from False to True, the drive is switched on at the full speed
specified at the Setpoint2 input (max. 100). You can toggle directly between Spd1 and Spd2 .
You can set the reduced drive speed as a percentage of between 0 and 100 at the analog input
Setpoint1. The default setting for this input is 70. You can set the full drive speed as a
percentage of between 0 and 100 at the analog input Setpoint2. The default setting for this input
is 100. If the speed values are not in these defined ranges, the message "Motor: Setpoint invalid
value" (message categoryERROR) is generated. The setpoints can be configured separately.
The binary output FbkSpd1 is only set to True if the drive has reached the preselected speed:
The value at analog output Y is identical to the value specified at the Setpoint1 input.
The binary output FbkSpd2 is only set to True if the drive has reached the preselected speed:
The value at analog output Y is identical to the value specified at the Setpoint2 input.
The binary outputsSpd1Local, Spd2Local and StopLocal only represent the duration of the key
operation to set the Speed 1, Speed 2 or Stop keys in the component operating window to True.
Operating window
The component operating window shows the current speed of the drive as a bar graph.
The left-hand column shows the two inputs LocalAct and LockAct. You can see the current
state pending here.
You can also separate both inputs from their sources and set the value manually.
If LocalAct (Local active) is enabled, the speed is no longer derived from the inputs of the
component. Instead, it is formed from the local operating buttons in the central column, Speed
1, Speed 2 and Stop. The specified start-up and run-down times remain effective. The switch
from remote to local is smooth: If the drive was on before switchover with Speed 1, it is initially
also on immediately switchover with Speed 1.
In the right-hand column is the operating switch for Local, maintenance (Maint) and Trip.
Many variable-speed drives are connected directly to the controller via PROFIBUS DP or
PROFINET. To standardize the configuration of such drives, a profile called PROFIdrive was
created by the PROFIBUS User Organization (PNO). This profile defines how a drive matching
this profile behaves on the field bus with regard to some of its more important functions. The
following power converters or frequency converters from the Siemens range of products meets
the requirements of a PROFIdrive:
● SIMOREG DC Master
● SIMOVERT Masterdrive
● Micromaster
● Sinamics
A common feature of all PROFIdrive devices is that they are activated by control words (STW)
and provide feedback in a status words (ZSW). In addition, the drives receive a speed setpoint
from the controller and provide the actual speed and an actual position as feedback.
The functionality of a PROFIdrive can be divided roughly into the following blocks:
● State machine
● Ramp generator for the transferred setpoint speed
● Position actual value preparation
Status diagram
S3: Switched On
S5: Ramp Stop
S4: Operation
Ramp generator
Some of the bits in the control and status words are not defined in the PROFIdrive profile. The
five bits 11 to 15 in the control and status word 1 can be drive-specific and may therefore have
different meanings according to the type of drive. For the SINAMICS and Universal AC
converters, these drive-specific functions are emulated in the corresponding device-specific
components. These drive-specific components are simply attached to the PROFIdrive header
component, as illustrated in the figure below.
In addition to the control and status word and the speed setpoint and actual speed values,
PROFIdrive devices can exchange other information with the controller. These additional I/O
signals are available in SIMIT through the SIMIT Unit coupling like standard I/O signals and can
therefore also be used for specific modification of a drive simulation.
3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3='
7(/B
1RPLQDO 67: 162//B$
7(/B
=6: 1,67B$
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67:
7(/B
=6: 1,67B% =6:
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67: *B67:
7(/B =6: 1,67B% =6: *B=6: *B;,67 *B;,67 *B=6: *B;,67 *B;,67
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67: *B67: ;(55 .3&
7(/B
=6: 1,67B% =6: *B=6: *B;,67 *B;,67
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67: *B67: *B67: ;(55 .3&
7(/B
=6: 1,67B% =6: *B=6: *B;,67 *B;,67 *B=6: *B;,67 *B;,67
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67: 0B5HG *B67:
7(/B =6: 1,67B% =6: 0HOGB: *B=6: *B;,67 *B;,67 *B=6: *B;,67 *B;,67
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67: 0B5HG *B67: ;(55 .3&
7(/B
=6: 1,67B% =6: 0HOGB: *B=6: *B;,67 *B;,67
$FWXDO
7(/B
1RPLQDO 67: 162//B% 67: 0B5HG *B67: *B67: ;(55 .3&
7(/B
=6: 1,67B% =6: 0HOGB: *B=6: *B;,67 *B;,67 *B=6: *B;,67 *B;,67
$FWXDO
Symbol
Function
Technological objects in the S7-1500 have a functionality with which they synchronize their
technological parameters with the technological parameters of the drive. This process is
referred to as data adaption. The DataAdaption component type supplies the required
information to the technology object using acyclic data record communication.
The DataAdaption component is always the last component to be added to a simulated drive.
Connectors
Input Description
Gateway Connection to the configuration of the drive component via a unit con‐
nector
DriveIn Structure for docking to upstream PROFIdrive components
Parameter
Parameters Description
ReferenceSpeed Here you enter the reference speed.
MaxSpeed Here you enter the maximum physical speed of the
drive.
G1_EncoderSystem Enter the type of encoder system here.
0 = rotary encoder system
1 = linear encoder system
G1_SupportsAbsolutValues Enter here whether encoder 1 is an
True = absolute encoder
False = incremental encoder
● u64 – unsigned64
● f64 – floating point
The following table shows the parameters provided by the DataAdaption component to the
technology object.
Symbol
Function
The DynamicServoControl component type is used to enhance a PROFIdrive telegram
according to the PROFIdrive profile (Technical Specification, Version 4.2, Edition: October
2015 (Order No.: 3.172)) by the functionality of the drive-internal controller.
7(/B
=6: 1,67B% =6: *B=6: *B;,67 *B;,67
$FWXDO
Telegrams with a higher value have been defined in the PROFIdrive profile; these can be used
to move the position control from the controller to the drive. This is of particular importance
when the cycle in which the technology application in the controller is reduced compared to the
bus clock.
Moving the position control from the controller to the drive necessarily requires an isochronous
bus system and that the SIMIT application is operated in bus synchronous mode. To do so, set
the bus synchronous operating mode (Page 45).
Connectors
Input Description
XERR Error signal from the PROFIdrive telegram
KPC Controller gain from the PROFIdrive telegram
DriveIn Structure for docking to upstream PROFIdrive components
Output Description
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameters Description
G1_FineResolutionXist1 Enter the fine resolution of G1_Xist1 here.
G1_FineResolutionXist2 Enter the fine resolution of G1_Xist2 here.
G2_FineResolutionXist1 Enter the fine resolution of G2_Xist1 here.
G2_FineResolutionXist2 Enter the fine resolution of G2_Xist2 here.
The parameter values should be consistent with the parameters of the same name of the
sensor block.
GeneralDrive
Symbol
Function
The GeneralDrive component type supplements the PROFIdrive block with the functionality of
a delay element. The actual speed is calculated internally on the basis of the specified setpoint,
so that an external connection of the NIst input on the PROFIdrive component is no longer
necessary.
TDelay is the delay with which the speed actual value tracks the effective setpoint value (ramp
function generator value from PROFIdrive block) via the delay function. The default delay time
is half a second.
The reference value at analog input RefVal is a percentage speed value. If the speed actual
value exceeds the reference value, bit 10 of the status word (ZSW1.10) is set to 1. The default
reference value is 5 percent. The switchover of this signal is performed using a configurable
hysteresis. This is also stated as a percentage speed value in the Hysteresis parameter. The
default hysteresis value is 3 percent.
Connectors
Input Description
TDelay Time constant of the delay time
RefVal Reference value set to one with bit 10 in status
word (ZSW1.10)
DriveIn Structure for docking to upstream PROFIdrive
components
Output Description
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameters Description
ReferenceSpeed Here you enter the reference speed.
RampTime Here you enter the ramp slope for changing the
speed setpoint.
EmergencyStopTime Here you enter the slope with which the pending
speed setpoint is to be reduced in case of an error.
Symbol
Function
The PROFIdrive1 component type simulates the state machine with the ramp function
generator according to the PROFIdrive profile (Technical Specification, Version 4.2, Edition:
October 2015 (Order No.: 3.172)).
Functionalities for Application Class 1 (AC1) "Standard Drive – Speed Control Mode" are
simulated.
This component therefore simulates the functionality defined in standard PROFIdrive telegram
1:
3=' 3='
7(/B
1RPLQDO 67: 162//B$
7(/B
=6: 1,67B$
$FWXDO
The starting point for configuring a PROFIdrive1 component is the controller access to the input
and output signals of the PROFIdrive drive. For each dive, a fixed address range is defined
within the controller input and output area, and assigned to a PROFIdrive1 component as
follows: The control word (first process data word in the output area) is connected to the integer
input STW1 and the status word (first process data word of the controller inputs) is connected
to the integer output ZSW1. The speed setpoint and actual speed values are transferred in the
second process data word. Accordingly, the integer input NSOLL_A is connected to the speed
setpoint value. The integer output NIST_A is connected to the speed actual value of the
controller.
In the figure below, an example of a SIMATIC configuration for SINAMICS is shown.
The figure below shows the PROFIdrive1 component and the connected process data:
The process data speed values, which means NSOLL_A and NIST_A are raw values in the
range zero to 16384. The value 16384 corresponds to the nominal speed. Other process data,
for example, torque values or actual current values, are not taken into account in the
PROFIdrive1 component.
The current speed of the drive is output as a percentage at analog output Y, in other words in
a range of 0 to 100: 0 ≤ Y ≤ 100. A value of 0 thus corresponds to a stationary drive, while a
value 100 corresponds to the nominal speed (raw speed value 16384).
The contents of the control word and the status word are displayed bit-by-bit in the operating
window of the component. In addition, the setpoint speed value NSOLL_A and the speed actual
value NIST_A, are displayed as percentage values and in revolutions per minute (RPM). The
fourth bit and eighth bit in the status word (ZSW1.3 - Fault and ZSW1.7 - Warning) can be set
to 1 using a toggle switch.
See also
Using the PROFIdrive library to simulate PROFIdrive drives (Page 466)
State machine
The state machine is described in detail in the PROFIdrive specification. The state graph
implemented in the PROFIdrive1 component type is illustrated in the figure below:
3RZHURQ
352),GULYH
6WDWXVGLDJUDP
66ZLWFKLQJ2Q,QKLELWHG
=6: =6:
=6: =6:
67: $1'
67: $1'
67:
67: 25
67:
65HDG\)RU6ZLWFKLQJ2Q
=6: =6: 67: 67:
=6: =6: 256WDQGVWLOO
67:
64XLFN6WRS
67: 25
67:
67:
67:
66ZLWFKHG2Q 67:
256WDQGVWLOO
=6: =6: 6ZLWFKLQJ2II
=6: =6: 65DPS6WRS =6: =6:
=6: =6:
67: 67:
67:
67:
62SHUDWLRQ
67: =6: =6: =6:[ %LW[LQVWDWXVZRUG
=6: =6: 67: 67:\ %LW\LQFRQWUROZRUG
3ULRULW\KLJKHVWORZHVW
The control bits shown in the table are used to control the state machine (status transitions).
Depending on the current status, the corresponding status bits are set as illustrated in the table.
The individual bits in status word STW1 shown in the table have the following meaning:
The meaning of all the status word bits is described in the table below.
Ramp generator
The ramp function generator (RFG) is controlled by bits 4, 5 and 6 of the control word (STW1.4,
STW1.5, STW1.6). Bit 6 sets the input of the generator to NSOLL_RFG. The generator then
ramps up or down to this setpoint value in a linear manner using the set time RampTime
assuming the generator is enabled via bit 5. Otherwise, the last output value of the generator
is retained. Finally, bit 4 determines whether the ramp generator value is output. A setpoint
connection can only be carried out in state S4. Otherwise the ramp setpoint 0 is output.
Connectors
Input Description
STW1 Control word 1 (STW1) from the PROFIdrive telegram
NSOLL_A Standardized speed setpoint (NSOLL_A) from the PROFI‐
drive telegram
NIst Process value actual speed
Output Description
ZSW1 Status word 1 (ZSW1) from the PROFIdrive telegram
NIST_A Standardized actual speed value (NIST_A) from the PROFI‐
drive telegram
Y Process value speed setpoint value specification relative to
the reference speed in %
NSoll Process value speed setpoint value specification
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameters Description
ReferenceSpeed Here you enter the reference speed.
MaxSpeed Here you enter the maximum physical speed of the drive.
RampTime Here you enter the ramp slope for changing the speed set‐
point.
EmergencyStopTime Here you enter the slope with which the pending speed set‐
point is to be reduced in case of an error.
HysteresisSpeed Enter here the width of the window which will be moved
around the target speed. If the actual speed is within this win‐
dow, ZSW.Bit8 (Speed Error Within Tolerance) is set to
TRUE.
SpeedThreshold Enter a comparison value for the speed threshold here. If the
actual speed has reached or exceeded this comparison val‐
ue, ZSW.Bit10 (Speed Reached) is set to TRUE.
Symbol
Function
The PROFIdrive2 component type simulates the state machine with the ramp function
generator according to the PROFIdrive profile (Technical Specification, Version 4.2, Edition:
October 2015 (Order No.: 3.172)).
In addition to the PROFIdrive1 block, the PROFIdrive2 block provides a monitoring option in
form of a sign-of-life signal exchange in STW2 and ZSW2.
The cyclic exchange of the sign-of-life requires that the SIMIT application is operated in bus
synchronous mode. To do so, set the bus synchronous operating mode.
This component therefore simulates the functionality defined in the standard PROFIdrive
telegram 2 that is used for operation of extended speed-controlled axes:
7(/B
=6: 1,67B% =6:
$FWXDO
Additional components are required for modeling positioning axes; these can be docked over
the special connector for expansion (see also Specific output for expansion (Page 487)).
State machine
The state machine is described in detail in the PROFIdrive specification. The state graph
implemented in the PROFIdrive2 component type is illustrated in the figure below:
3RZHURQ
352),GULYH
6WDWXVGLDJUDP
66ZLWFKLQJ2Q,QKLELWHG
=6: =6:
=6: =6:
67: $1'
67: $1'
67:
67: 25
67:
65HDG\)RU6ZLWFKLQJ2Q
=6: =6: 67: 67:
=6: =6: 256WDQGVWLOO
67:
64XLFN6WRS
67: 25
67:
67:
67:
66ZLWFKHG2Q 67:
256WDQGVWLOO
=6: =6: 6ZLWFKLQJ2II
=6: =6: 65DPS6WRS =6: =6:
=6: =6:
67: 67:
67:
67:
62SHUDWLRQ
67: =6: =6: =6:[ %LW[LQVWDWXVZRUG
=6: =6: 67: 67:\ %LW\LQFRQWUROZRUG
3ULRULW\KLJKHVWORZHVW
The control bits shown in the table are used to control the state machine (status transitions).
Depending on the current status, the corresponding status bits are set as illustrated in the table.
The individual bits in status word STW1 shown in the table have the following meaning:
The meaning of all the status word bits is described in the table below.
Ramp generator
The ramp function generator (RFG) is controlled by bits 4, 5 and 6 of the control word (STW1.4,
STW1.5, STW1.6). Bit 6 sets the input of the generator to NSOLL_RFG. The generator then
ramps up or down to this setpoint value in a linear manner using the set time RampTime
assuming the generator is enabled via bit 5. Otherwise, the last output value of the generator
is retained. Finally, bit 4 determines whether the ramp generator value is output. A setpoint
connection can only be carried out in state S4. Otherwise the ramp setpoint 0 is output.
Connectors
Input Description
STW1 Control word 1 (STW1) from the PROFIdrive telegram
NSOLL_B Standardized speed setpoint (NSOLL_B) from the PROFIdrive telegram
STW2 Control word 2 (STW2) from the PROFIdrive telegram
NIst Process value actual speed
Output Description
ZSW1 Status word 1 (ZSW1) from the PROFIdrive telegram
NIST_B Standardized speed actual value (NIST_B) from the PROFIdrive tele‐
gram
ZSW2 Status word 2 (ZSW2) from the PROFIdrive telegram
Y Process value speed setpoint value specification relative to the refer‐
ence speed in %
NSoll Process value speed setpoint value specification
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameters Description
ReferenceSpeed Here you enter the reference speed.
MaxSpeed Here you enter the maximum physical speed of the drive.
RampTime Here you enter the ramp slope for changing the speed set‐
point.
EmergencyStopTime Here you enter the slope with which the pending speed set‐
point is to be reduced in case of an error.
Symbol
Function
The Safety30 component type is used to enhance a PROFIdrive telegram according to the
PROFIdrive profile (Technical Specification, Version 4.2, Edition: October 2015 (Order No.:
3.172)) by the functionality of Safety telegram 30.
This block processes user data of Safety telegram 30. The simulation of the PROFISafe trailer
is not performed. Simulation of the secure PROFISafe communication is not required to use
PLCSIM_Adv.
Connectors
Input Description
S_STW1 Safety control word 1
DriveIn Structure for docking to upstream PROFIdrive components
Output Description
S_ZSW1 Safety status word 1
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameter Description
SafetyTimeout Monitoring time of an active Safety function in ms
STO_Enabled Support for the Safety Integrated Function Safe Torque Off (STO)
SS1_Enabled Support for the Safety Integrated Function Safe Stop 1 (SS1)
SS2_Enabled Support for the Safety Integrated Function Safe Stop 2 (SS2)
Parameter Description
SOS_Enabled Support for the Safety Integrated Function Safe Operating Stop (SOS)
SLS_Enabled Support for the Safety Integrated Function Safely-Limited Speed (SLS)
SLT_Enabled Support for the Safety Integrated Function Safely-Limited Torque (SLT)
SLP_Enabled Support for the Safety Integrated Function Safely-Limited Position (SLP)
SLA_Enabled Support for the Safety Integrated Function Safely-Limited Acceleration
(SLA)
SDI_Enabled Support for the Safety Integrated Function Safely – Safe Direction (SDI)
Symbol
Function
The Safety31 component type is used to enhance a PROFIdrive telegram according to the
PROFIdrive profile (Technical Specification, Version 4.2, Edition: October 2015 (Order No.:
3.172)) by the functionality of Safety telegram 31.
This block processes user data of Safety telegram 31. The simulation of the PROFISafe trailer
is not performed. Simulation of the secure PROFISafe communication is not required to use
PLCSIM_Adv.
Connectors
Input Description
S_STW2 Safety control word 2
DriveIn Structure for docking to upstream PROFIdrive components
Output Description
S_ZSW2 Safety status word 2
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameter Description
SafetyTimeout Monitoring time of an active Safety function in ms
STO_Enabled Support for the Safety Integrated Function Safe Torque Off (STO)
SS1_Enabled Support for the Safety Integrated Function Safe Stop 1 (SS1)
SS2_Enabled Support for the Safety Integrated Function Safe Stop 2 (SS2)
Parameter Description
SOS_Enabled Support for the Safety Integrated Function Safe Operating Stop (SOS)
SLS_Enabled Support for the Safety Integrated Function Safely-Limited Speed (SLS)
SLT_Enabled Support for the Safety Integrated Function Safely-Limited Torque (SLT)
SLP_Enabled Support for the Safety Integrated Function Safely-Limited Position (SLP)
SLA_Enabled Support for the Safety Integrated Function Safely-Limited Acceleration
(SLA)
SDI_Enabled Support for the Safety Integrated Function Safely – Safe Direction (SDI)
Symbol
Function
The Safety32 component type is used to enhance a PROFIdrive telegram according to the
PROFIdrive profile (Technical Specification, Version 4.2, Edition: October 2015 (Order No.:
3.172)) by the functionality of Safety telegram 32.
This block processes user data of Safety telegram 32. The simulation of the PROFISafe trailer
is not performed. Simulation of the secure PROFISafe communication is not required to use
PLCSIM_Adv.
Connectors
Input Description
S_STW2 Safety control word 2
DriveIn Structure for docking to upstream PROFIdrive components
Output Description
S_ZSW2 Safety status word 2
S_XIST32 Safety position of current value (for Safety telegram 32)
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameter Description
SafetyTimeout Monitoring time of an active Safety function in ms
STO_Enabled Support for the Safety Integrated Function Safe Torque Off (STO)
SS1_Enabled Support for the Safety Integrated Function Safe Stop 1 (SS1)
Parameter Description
SS2_Enabled Support for the Safety Integrated Function Safe Stop 2 (SS2)
SOS_Enabled Support for the Safety Integrated Function Safe Operating Stop (SOS)
SLS_Enabled Support for the Safety Integrated Function Safely-Limited Speed (SLS)
SLT_Enabled Support for the Safety Integrated Function Safely-Limited Torque (SLT)
SLP_Enabled Support for the Safety Integrated Function Safely-Limited Position (SLP)
SLA_Enabled Support for the Safety Integrated Function Safely-Limited Acceleration
(SLA)
SDI_Enabled Support for the Safety Integrated Function Safely – Safe Direction (SDI)
G1_EncoderSystem Enter the type of encoder system here.
0 = rotary encoder system
1 = linear encoder system
Symbol
Function
The SafetyProcess component type is used to resolve errors during active drive-internal Safety
functions.
The component must be connected to the Process connector of a Safety component from the
PROFIdrive telegram.
Connectors
Input Description
S_PositionOffsetError Resolution of a position monitoring error during an active Safety Inte‐
grated function: Safe Operating Stop (SOS)
S_SpeedLimitError Resolution of a speed monitoring error during an active Safety Integra‐
ted function: Safely-Limited Speed (SLS)
S_TorqueLimitError Resolution of a torque limit violation during an active Safety Integrated
function: Safely-Limited Torque (SLT)
S_SpeedDirPError Resolution of a direction reversal (negative) during an active Safety
Integrated function: Safe Direction (SDI)
S_PositionLimitError Resolution of a position limit violation during an active Safety Integrated
function: Safely Limited Position (SLP)
S_SpeedDirNError Resolution of a direction reversal (positive) during an active Safety In‐
tegrated function: Safe Direction (SDI)
Output Description
Safety Output structure for the interconnection to the Process connector of a
Safety component from the PROFIdrive telegram.
Symbol
Function
The Sensor component type is used to enhance a PROFIdrive telegram according to the
PROFIdrive profile (Technical Specification, Version 4.2, Edition: October 2015 (Order No.:
3.172)) by the functionality of a sensor.
This component therefore simulates the part of a sensor in the standard PROFIdrive telegram:
If a telegram is to be simulated with two sensors, this can be done by docking an additional
"Sensor" component.
3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3='
7(/B
1RPLQDO
67: 162//B% 67: *B67: *B67:
7(/B =6: 1,67B% =6: *B=6: *B;,67 *B;,67 *B=6: *B;,67 *B;,67
$FWXDO
Connectors
Input Description
Gx_STW Sensor control word (Gx_STW) from the PROFIdrive telegram
Process Structure for docking a sensor simulation
DriveIn Structure for docking to upstream PROFIdrive components
Output Description
Gx_ZSW Sensor status word (Gx_ZSW) from the PROFIdrive telegram
Gx_XIST1 Sensor actual value 1 (Gx_XIST1) from the PROFIdrive telegram
Gx_XIST2 Sensor actual value 2 (Gx_XIST2) from the PROFIdrive telegram
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameters Description
GxFineResolutionXist1 Enter the fine resolution of Gx_Xist1 here.
GxFineResolutionXist2 Enter the fine resolution of Gx_Xist2 here.
Symbol
Function
The SensorProcessLinear component type is used to simulate the functionality of a linear
encoder. You can simulate linear absolute encoders as well as linear incremental encoders.
The component must be connected to the ""Process"" connector of a "Sensor" (Page 492)
component from the PROFIdrive telegram.
Connectors
Input Description
Gx_XIST Process value in the engineering unit mm
Gx_ReferenceMark1…4 Encoder reference marks 1–4 (TRUE = reference mark deflected)
Gx_Probe1..2 Measuring probe deflection 1–2 (TRUE = measuring probe deflected)
Gx_ErrorCode Simulated encoder error code
Output Description
Sensor Output structure for connection to the "Process" connector of a "Sensor"
(Page 492) component from the PROFIdrive telegram.
Parameter
Parameter Description
DistanceBetweenIncrements Here you enter the distance between two tick marks in millimeters.
SupportsAbsoluteValues Here you enter whether an absolute (=TRUE) or an incremental
(=FALSE) encoder is to be simulated.
Symbol
Function
The SensorProcessRotatory component type is used to simulate the functionality of a rotary
encoder. You can simulate rotary absolute encoders as well as rotary incremental encoders.
The component must be connected to the "Process" connector of a "Sensor" (Page 492)
component from the PROFIdrive telegram.
Connectors
Input Description
Gx_XIST Process value of a physical variable
Gx_ReferenceMark1…4 Encoder reference marks 1–4 (TRUE = reference mark deflected)
Gx_Probe1..2 Measuring probe deflection 1–2 (TRUE = measuring probe deflected)
Gx_ErrorCode Simulated encoder error code
Output Description
Sensor Output structure for connection to the ""Process"" connector of a "Sen‐
sor" (Page 492) component from the PROFIdrive telegram.
Parameters
Parameter Description
IncrementsPreRevolution Here you enter the encoder property encoder line per revolution.
DeterminableRevolutions Here you enter the number of revolutions for rotary encoders in which
the absolute value can be determined.
DistancePerRevolution Here you enter the distance in the physical unit you have selected that
is covered in one encoder revolution (e.g. 360.0 for 360°).
SupportsAbsoluteValues Here you enter whether an absolute (=TRUE) or an incremental
(=FALSE) encoder is to be simulated.
Symbol
Function
The Universal component type can only be meaningfully used in combination with
the PROFIdrive1orPROFIdrive2 component type. It enables drive-specific functions to be
realized in addition to the basic PROFIdrive functions.
Bits 11 to 15 of the control word (STW1.11–15), the speed setpoint value NSOLL_A and the
speed actual value NIST (NIST_PT1) are placed on the outputs of the Universal component. By
means of appropriate logical and arithmetical operations, bits 11 to 15 of the status word, the
speed setpoint value NSOLL (NSOLL_RFG), and the speed actual value NIST_A are set at the
inputs of the component. The signal linkage resulting from the connection of the
Universalcomponent to the PROFIdrive component is illustrated in the figure below.
8QLYHUVDO
The figure below illustrates an example of how the drive-specific functions for the Type 3
Micromaster can be implemented with the aid of the Universal component.
Siemens
InFeed_Tel_370
Symbol
Function
The Infeed_Tel_370 component type simulates an electrical infeed unit that is switched on and
off by commands that are transported by the PROFIdrive telegram 370.
Telegram structure p922=370
To signal a warning or error situation, set the binary input Warning or Fault from False to True.
When the binary input Close Line Contactor is set to True, the electrical infeed unit requests that
the line contactor is closed. This request must be fed back to the binary input Line Contactor
closed. This is done through a direct connection or by using a delay block to simulate in more
detail.
Dialog box
The "Infeed_Tel_370" dialog box shows the current status of the control and status words in
telegram 370.
Symbol
Function
The SiemensMomentumReduction component type is used to enhance a PROFIdrive
telegram according to the PROFIdrive profile (Technical Specification, Version 4.2, Edition:
October 2015 (Order No.: 3.172)) by the manufacturer-specific functionality for the
transmission of a torque reduction value.
7(/B
=6: 1,67B% =6: *B=6: *B;,67 *B;,67
$FWXDO
Connectors
Input Description
MOMRED Standardized torque reduction specification from the PROFIdrive tele‐
gram
DriveIn Structure for docking to upstream PROFIdrive components
Output Description
MELDW Currently not used and is always 0
M_RED Reduced torque with reference to Torque_RedScale parameter
M_Lower_Limit Reduced low torque limit
M_Upper_Limit Reduced high torque limit
DriveOut Structure for connecting additional PROFIdrive components
Parameter
Parameter Description
Torque_Nominal Here you enter the reference torque.
Torque_UpperLimit Here you enter the top physical speed limit of your drive.
Torque_LowerLimit Here you enter the low physical speed limit of your drive.
Torque_RedScale Here you specify the percentage to which the torque reduction is to be
normalized. The reference torque is typically 100%.
Symbol
Function
The specific additional functions for the SINAMICS frequency converter are implemented in
the Sinamics component type. The implementation is coordinated with the processing stages
contained in the SINA_GS function block. The SINA_GS function block is located in the function
block library DriveES-PCS 7 .
The Sinamics component type can only be used in combination with the PROFIdrive1 or
PROFIdrive2 component type.
STW1.11 NSOLL
Inversion of setpoint value
0 NSOLL
1 −NSOLL
The speed actual value NIst and the bit 11 of the status word are set according to the
relationships listed in the table below.
NIst ZSW1.11
Positive direction of rotation
NIst >= 0 1
NIst < 0 0
Symbol
Function
The specific additional functions for the SIMOREG DC Master power converter are
implemented in the DCMaster component type. The implementation is adapted to the
processing steps contained in the SIMO_DC function block from the Drive ES PCS 7 function
block library.
The DCMaster component type can only be used in combination with the PROFIdrive1 or
PROFIdrive2 component type.
The speed actual value NIst and the bits 12 and 14 of the status word are set according to the
relationships listed in the table below.
Symbol
Function
The specific additional functions for the SIMOVERT Masterdrive frequency converter are
implemented in the Masterdrive component type. The implementation is coordinated with the
processing stages contained in the SIMO_MD function block. The SIMO_MD function block is
located in the function block library DriveES-PCS7.
The Masterdrive component type can only be used in combination with the PROFIdrive1 or
PROFIdrive2 component type.
The speed actual value NIst and the bits 12 and 14 of the status word are set according to the
relationships listed in the table below.
Symbol
Function
The specific additional functions for the MICROMASTER Type 3 frequency converter are
implemented in the Micromaster3 component type. The implementation is coordinated with the
processing stages contained in the SIMO_MM3 function block. The SIMO_MM3 function block
is located in the function block library DriveES-PCS7.
The Micromaster3 component type can only be used in combination with the PROFIdrive1 or
PROFIdrive2 component type.
STW1.14 NSOLL
Clockwise rotation
0 - NSOLL
1 NSOLL
The speed actual value NIst and the bit 14 of the status word are set according to the
relationships listed in the table below.
NIst ZSW1.14
Clockwise rotation
NIST >= 0 1
NIST < 0 0
Symbol
Function
The specific additional functions for the MICROMASTER Type 4 frequency converter are
implemented in the Micromaster4 component type. The implementation is coordinated with the
processing stages contained in the SIMO_MM4 function block. The SIMO_MM4 function block
is located in the function block library DriveES-PCS7.
The Micromaster4 component type can only be used in combination with the PROFIdrive1 or
PROFIdrive2 component type.
STW1.11 NSOLL
Inversion of setpoint value
0 NSOLL
1 - NSOLL
The speed actual value NIst and the bit 11 of the status word are set according to the
relationships listed in the table below.
NIst ZSW1.11
Positive direction of rotation
NIST >= 0 1
NIST < 0 0
SIMOCODE pro motor management and control devices are used to switch motors on and off
and to monitor the resulting currents. As an option, SIMOCODE pro can also be used to record
other measured values and to access comprehensive statistical evaluations. A SIMOCODE
pro device is connected to the controller as an individual PROFIBUS DP slave.
By configuring the device accordingly, a SIMOCODE pro can be employed for very different
tasks. For example, it can operate as direct-on-line starter, reversing starter, star-delta starter
with or without reversal of rotation, pole switching device with or without reversal of rotation, as
well as positioner, solenoid valve drive, overload relay or power circuit breaker. The directory
SIMOCODEpro in the Drives Library contains component types that emulate the various
control functions of SIMOCODE pro. These component types form the SIMOCODEpro Library
of SIMIT.
67: =6:
2QRIIVZLWFKLQJORJLF
&RQWUROGDWD 0HVVDJHGDWD
$FWXDOFXUUHQW
&XUUHQW>@
6SHHG
5XQXSWLPH
5XQGRZQWLPH
The corresponding connectors of the SIMOCODEpro component types can be seen in the
symbols depicted in the figure below.
All SIMOCODE pro devices are accessed via control data and return their current status to the
controller by means of message data. The content of the control and message data depends
on which control function is implemented. Only the cyclical control and message data is
processed by the SIMOCODEpro component types; acyclical data such as statistical data, for
example, are not taken into account. The components can interface with the controller in the
following ways:
● The control data word (2 bytes) of the controller outputs is connected to the integer
input STW of the component.
● The first data word of the message data in the controller inputs contains the binary feedback
and is connected to the integer output ZSW. Analog message data, for example, the actual
current value, is transferred to the controller in the second data word.
This configuration corresponds to SIMOCODE pro C or, in the case of SIMOCODE pro V, to
basic type 2.
In the figure below, an example of a SIMATIC configuration for a Dahlander motor is shown.
The figure below shows the SIMOCODEpro component and the associated process data.
The actual current I is communicated to the controller as a percentage value of the current
setting (rated motor current). The current value at input I is interconnected as the actual current
to the output I, provided that the motor is switched on. The input has a default value of 100%,
which means the actual current equals the current setting. The switching on and off of the motor
is controlled by a ramp function.
The relationship between current and motor load is not taken into account. This can however
easily be added in the simulation, for example, by not setting the current as a constant value but
by using suitable functions to make it dependent on the motor speed or on the process instead.
You can find additional information on this in section: Individual adaptations (Page 510).
The speed of the motor is available as a percentage value at output Y of a SIMOCODEpro
component. The run-up and run-down times of the motor are set on the two analog inputs TUp
and TDown. TUp is the time in seconds it takes the motor to run up from standstill to the nominal
speed; TDown is the time in seconds it takes for the motor to run down to a standstill from the
nominal speed. Both times have a default value of one second. If one of the two input values
is negative during the simulation, the message "x: run-up or run-down time invalid value"
(message category ERROR) is generated.
Note
In the case of positioners and solenoid valves, the run-up and run-down times mean the
opening and closing time TUp and TDown of the valve.
The speed of the motor is not specified by the controller nor detected by the SIMOCODE pro
devices. The speed value is therefore not communicated to the controller. Its purpose is to
provide another source of motor speed input for the simulation. Consequently, the run-up and
run-down times are only of minor importance.
Switchover pauses and interlock times are ignored by the SIMOCODEpro component types.
Corresponding feedback for the controller is not generated.
Ramp function
The motor speed is formed using a ramp function. The most general form of this ramp for a drive
with two speeds in two directions of rotation is illustrated in the figure below.
The increase and decrease times of the ramp correspond to the run-up and run-down times TUp
and TDown of the motors. Depending on how SIMOCODE pro is configured, the motor speed Y
is generated as a percentage value in the range –100% to 100%.
Overload behavior
Overload can be set using the Overload switch in the operating window of a component. The
motor is switched off in the event of an overload. A thermal switch-on inhibitor determines when
the motor can be switched on again (cooling down time). The cooling down time begins when
the overload no longer exists. The cooling down time is set in the Cool_Down_Period parameter
and has a default value of 300 seconds, as shown in the figure below.
As shown in the figure below, the remaining cooling down time is displayed in the Cool down
field of the operating window:
During this time the drive is disabled, which means it cannot be restarted.
The thermal switch-on inhibitor is reset by setting the emergency start (EM-Start, STW.12) bit.
The drive can be restarted immediately.
The advance warning for overload (I >115%, ZSW.11) is set as soon as the input current
exceeds 115%.
The test function Test1 resets the SIMOCODE pro device five seconds after setting the signal.
The motor is switched off.
Setting EM-Start resets the thermal switch-on inhibitor if it has been triggered by an overload.
The motor can then be switched on again immediately.
The Remote command displays the controller default for operating mode switch S1. This
command has no functional effect on the simulation.
The SIMOCODE pro device is reset using the Reset command. This switches the motor off.
The table below provides an overview of the standard message data for all SIMOCODEpro
component types. The overload advance warning does not apply to solenoid valves.
If the current value rises above 115%, bit ZSW.11 is set as advance warning of an overload.
The Remote, Fault and Warning signals can be set in the operating window of the component.
The Remote signal has a default value of one, which means the switch is closed.
Individual adaptations
Depending on how parameters have been assigned to a SIMOCODE pro device, signals in the
control and message data can have meanings that are not present in the SIMOCODEpro
Library components. However, these signals can be included in the simulation by a simple
connection to other components from the SIMIT Basic Library.
In the example of a ReversingDahlander component illustrated in the figure below, the
interlocking time and the change-over pause can be set manually. Neither signal is set in the
component. Here, the status word on the output of the component has been divided into its
individual signals by the conversion components (Word2Byte, Byte2Bit). The signals set in the
component are converted into a word again by the signals linked via the global connectors, and
communicated to the IW516 signal input of the automation system.
An example is also shown of how the current on the input of the ReversingDahlander
component can be mapped from the speed of the motor on output Y of the ReversingDahlander
component using a suitable trend function (Characteristic) and adjusted as required.
Symbol
Function
The component type DirectStarter simulates drives that have a single direction of rotation and
can be switched on and off directly. The table below provides an overview of the relevant control
data STW and message data STW for this application.
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the command "Switch on drive" (On, STW.10).
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched on. If the drive is switched off, it is set to zero. The speed value at the output Y is
formed as a percentage value with the help of the ramp function: 0 ≤ Y ≤ 100.
Symbol
Function
The ReversingStarter component type simulates drives with two directions of rotation, which
can be switched on and off directly in both directions. The table below provides an overview of
the relevant control data STW and message data ZSW for this application.
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the command "Switch on counterclockwise rotation" or "Switch on clockwise rotation"
(On<, STW.8 or On>, STW.10). Simultaneous switch-on commands for both directions of
rotation do not alter the status of the drive; they are ignored.
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched on in one of the two directions of rotation. If the drive is switched off, the actual
current value is set to zero. The speed value at the output y is formed as a percentage value
with the help of the ramp function: −100 ≤ Y ≤ 100.
Symbol
Function
The StarDeltaStarter component type simulates drives with star-delta switchover. The table
below provides an overview of the relevant control data STW and message data STW for this
application.
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the command "Switch on drive" (On, STW.10).
The maximum time for star mode is set in the parameter Max_Star_Time. The default time is 15
seconds. The switchover to delta mode (STW.10) is performed when the maximum star mode
time has been reached or if a value of less than 90% is present on the current input.
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched on. If the drive is switched off, the actual current value is set to zero. The speed
value at the output Y is formed as a percentage value with the help of the ramp function: 0 ≤ Y
≤ 100.
Symbol
Function
The ReversingStarDelta component type simulates drives with star-delta switchover in both
directions of rotation. The table below provides an overview of the relevant control data STW
and message data ZSW for this application.
Table 8-30 Control and message data for the ReversingStarDelta component
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the command "Switch on counterclockwise rotation" or "Switch on clockwise rotation"
(On<, STW.8 or On>, STW.10). Simultaneous switch-on commands for both directions of
rotation do not alter the status of the drive; they are ignored.
The maximum time for star mode is set in the parameter Max_Star_Time. The default time is 15
seconds. The direction-dependent switchover to delta mode (ZSW.10 or ZSW.8) is performed
when the maximum star mode time has been reached or if a value of less than 90% is present
at the current input.
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched on in one of the two directions of rotation. If the drive is switched off, the actual
current value is set to zero. The speed value at the output y is formed as a percentage value
with the help of the ramp function: −100 ≤ Y ≤ 100.
Symbol
Function
The Dahlander component type simulates drives with a single direction of rotation and two
speeds: full speed and low speed. The table below provides an overview of the relevant control
data STW and message data ZSW for this application.
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the commands "Switch to full speed" (On>>, STW.8) or "Switch to low speed" (On>,
STW.10). Simultaneous switch-on commands for both speeds do not alter the status of the
drive; they are ignored.
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched to one of the two speeds. If the drive is switched off, the actual current value is set
to zero.
The low speed nLow is set as a percentage value on the input Low speed. The default low speed
value is 50%. The speed value at the output Y is formed as a percentage value with the help of
the ramp function: 0 ≤ Y ≤ 100.
Symbol
Function
The ReversingDahlander component type simulates drives with two speeds of rotation in two
directions. The table below provides an overview of the relevant control data STW and
message data ZSW for this application.
Table 8-32 Control and message data for the ReversingDahlander component
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the switch-on commands "Full speed counterclockwise" (On<<, STW.0), "Low speed
counterclockwise" (On<, STW.2), "Full speed clockwise" (On>>, STW. 8) and "Low speed
clockwise" (On >, STW.10). Several simultaneous switch-on commands do not alter the status
of the drive; they are ignored.
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched on. If the drive is switched off, the actual current value is set to zero.
The low speed nLow is set as a percentage value on the input Low speed. The default low speed
value is 50%. The speed value at the output Y is formed as a percentage value with the help of
the ramp function: −100 ≤ Y ≤ 100.
Symbol
Function
The OverloadRelay component type simulates drives with overload monitoring. The Overload
command triggers an overload, which means the drive is switched off. The Restart command
switches the drive on. The commands can only be set in the operating window of the
component.
The drive can be initialized as switched on or switched off using the Initial_Value parameter:
switched on with the value Closed, switched off with the value Open. The default setting for
Initial_Value is Closed.
The actual current value at output I is set to the value at the current input I as soon as the drive
is switched on. If the drive is switched off, the actual current value is set to zero.
The speed value on the output Y is set to one hundred if the drive is on and to zero if the drive
is off.
Symbol
Function
The CircuitBreaker component type simulates drives with switching characteristics. The table
below provides an overview of the relevant control data STW and message data ZSW for this
application.
The commands "Open switch" (Off, STW.9) and "Reset" (RESET, STW.14) have priority over
the closing command (On, STW.10).
The switch can be initialized as closed or open using the Initial_Value parameter: closed with
the value Closed, opened with the value Open. The default setting for Initial_Value is Closed.
The actual current value at output I is set to the value at the current input I as soon as the switch
closes. If the switch is opened, the actual current value is set to zero.
The speed value on the output Y is set to one hundred if the drive is on and to zero if the drive
is off.
Symbol
Function
The Positioner component type simulates positioning drives for slide valves, adjusting valves,
etc. The table below provides an overview of the relevant control data STW and message
data ZSW for this application.
The commands "Switch off drive" (Off, STW.9) and "Reset" (RESET, STW.14) have priority
over the opening and closing commands (Open, STW.10 and Close, STW.8). Simultaneously
set opening and closing commands do not alter the status of the drive; they are ignored.
The actual current value at the output I is set to the value at the current input "I as long as the
slide valve is opening (ZSW.0) or closing (ZSW.2). The actual current value is set to zero if the
slide valve is stationary and when it is closed or open.
The position value at the output Y is formed as a percentage value with the help of a ramp
function: 0 ≤ Y ≤ 100. The value zero represents a closed slide valve, the value one hundred
an opened slide valve. The default opening and closing times of the slide valves are both set
to one second.
Symbol
Function
The Valve component type simulates drives for solenoid valves. The table below provides an
overview of the relevant control data STW and message data STW for this application.
The commands "Close valve" (Close, STW.9) and "Reset" (RESET, STW.14) have priority over
the opening command (Open, STW.10 and Close, STW.8).
The valve can be initialized as closed or open using the Initial_Value parameter: closed with the
value Closed, opened with the value Open. The default setting for Initial_Value is Closed.
The setting value at the output Y is formed as a percentage value with the help of a ramp
function.
0 ≤ Y ≤ 100
The value zero represents a closed valve, the value one hundred an opened valve.
The default opening and closing times of the solenoid valve are zero, which means the opening
and closing of the valve is done with a high gradient.
The Valve component does not have a current monitoring function and therefore no overload
behavior, neither does it have a current input nor a current output.
The SIWAREX U weighing system is used, for example, to measure fill levels in silos and
bunkers, to monitor crane loads and for overload protection of industrial lifts. In all these
applications, weights are detected with sensors such as load cells or force transducers and
transferred to the controller as measured values. Pressure-sensitive sensors deliver a voltage
proportional to the weight, which is converted by an analog/digital converter into a numerical
value, processed and sent to the controller. The voltage signal is converted and prepared with
the help of the SIWAREX U module. SIWAREX U modules can be connected to the PROFIBUS
DP via ET 200M or used as a module of the SIMATIC S7-300.
The aim of the simulation with SIWAREXU components is to send measured values – which in
the real system are transferred to the controller with the SIWAREX U weighing system – to the
controller as simulated values. The SIWAREX directory of the basic library includes two
component types for simulating the SIWAREX U weighing module:
● SIWAREXU1
● SIWAREXU2
These two component types simulate basic functions of the single-channel and two-channel
versions of the SIWAREX U weighing module. The function is the same for both component
types SIWAREXU1 and SIWAREXU2. Type SIWAREXU2 has one additional measuring
channel than type SIWAREXU1. The detailed descriptions below for one channel of the type
SIWAREXU1 therefore apply to both channels of the type SIWAREXU2 component type.
Symbol
Function
The SIWAREX U components simulate the following functions of the weighing system:
● Linear characteristic of the weighing system (adjustment diagonal)
● Zero offset,
● Decimal point shift
● Two configurable limits.
A function chart for a measuring channel of the component type is shown in the figure below.
6FDOLQJ /LPLW
39 'LJLWV
3URFHVVYDOXH
=HURYDOXH =HURSRLQWRIIVHW
'HFLPDOSRLQW
PHPRU\
RIIVHW
&0' *URVV
S
6HWWLQJWR]HUR
'LVSOD\YDOXH
/LPLWV
6WDWH
/LPLW
/LPLW
In the SIWAREX U weighing system, the weight to be measured is first converted by a pressure
sensor into an electrical voltage and then by an analog/digital converter into a numerical value.
In the simulation the numerical value of a weight is already available as the result of a model
calculation. The electrical signal transfer between the weighing sensor and the SIWAREX U
module is therefore irrelevant for the simulation: the calculated weight value is applied directly
to input PV of a SIWAREXU component as a physical measured variable.
The low-pass filtering and floating average calculation in the SIWAREX U module are not
required as fault suppression measures for the electrical voltage signal in the simulation.
Therefore neither function is included in the component types.
The weight value is available in Digits as a scaled numerical value limited to the range of zero
to 65,535. Scaling is carried out with the help of the linear characteristic of the weighing system
(adjustment diagonals). Furthermore, after any decimal point shift and zero offset, the weight
value Gross is an integer value limited to the range of –32,768 to +32,767.
See also
Access to a data record or memory area (Page 188)
As shown in the figure below, the assigned SIWAREXU component has a Unit connector at its
Unit input.
In the property view of the Unit connector, the component can be easily linked with the data
records in the coupling by entering the name of the Coupling and, under addressing the
subsystem number, enter the slave number and slot number in the form [#][#][#], which means
[1][40][4] for the example (see figure below).
A second way to link a SIWAREX component to the data records is provided by the SIMIT Unit
coupling itself. Open the SIMIT Unit coupling and its property view. In the navigation area on the
left, select the SIWAREX U module that is to be linked to the component by clicking on the
module entry with the left mouse button.
Hold down the left mouse button and drag this module onto the (previously opened) chart that
contains the component. The module is instantiated there as a Unit connector, which can be
directly connected to the Unit input of the SIWAREXU component. The Unit connector is
automatically provided with the address of the module.
Adjustment
Conversion of a weight value to a scaled Digit value is done using an adjustment diagonal
defined by two points.
3URFHVV
YDOXH
$GMXVWPHQWGLDJRQDO
$GMXVWPHQW
ZHLJKW
$GMXVWHG
VFDOHV]HUR
SRLQW
'LJLWV
$GMXVWPHQWGLJLW $GMXVWPHQWGLJLW
The first adjustment point is defined by the unloaded (empty) scale with only its inherent weight,
the second point by the selected adjustment weight. The corresponding scaled numerical
values are stored in the weighing module as adjustment digit 0 and adjustment digit 1.
In the simulation, adjustment is carried out by setting the adjustment parameters. The table
below lists the adjustment parameters of the SIWAREXU component types and their default
values.
Parameter Default
CH1_Dig_0 CH2_Dig_0 Adjustment digit 0 63107
CH1_Dig_1 CH2_Dig_1 Adjustment digit 1 2427
CH1_Adj_W CH2_Adj_W Adjustment weight 10000
The parameters for the adjustment digits are preset to values that correspond to a scale with
"theoretical adjustment" without zero offset. The adjustment weight is preset to a value of
10000 weight units.
Because the scales simulated with the SIWAREXU component types are calibrated by setting
permanently valid parameters, the simulated scales are always deemed to be calibrated.
Therefore a scale adjustment process initiated by the controller is pointless in the simulation.
Any such commands of the controller are ignored by the SIWAREXU components.
Zero offset
When a SIWAREXU component receives the "Set to zero" command via the CMD control word,
the weight value applied at that moment is saved as a new zero point. Consequently the zero
value is now output as a gross value. All subsequent measurements then relate to this value,
which means the difference between the current weight value and the zero value last saved is
output as the gross value.
The zero value used on starting the simulation can be set as a digit value in the CH1_Zero
parameter of the component. A default digit value of 2427 is set, corresponding to a weight
value of the unloaded scale assumed to be zero.
The decimal point shift is defined by the parameter CH1_Adjust according to the table below.
The default value is 65, which means no decimal point shift.
Note
If you change the default setting of the CH1_Adjust parameter in SIMIT, you must also change
the C1ADJUST parameter in the instance data block of the controller.
Limits
SIWAREX U has two adjustable limits whose switch-on and switch-off points can be freely
specified in weight units. The setting "Switch on value > Switch off value" leads to a notification
when a weight value is overshot:
0HVVDJH
21
*URVV
2))
2)) 21
The setting "Switch off value > switch on value" leads to a notification when a weight value is
undershot:
0HVVDJH
21
*URVV
2))
2)) 21
In the special case where the limits for OFF and ON are equal, limit 1 signals an exceedance
of this value while limit 2 signals that the set value has been undershot.
The limits a specified with the parameters CH1_ON_L1 and CH1_OFF_L1 for the first limit and
with the parameters CH1_ON_L2 and CH1_OFF_L2 for the second limit. The default values are
shown in the table below.
Parameter Default
CH1_ON_L1 CH2_ON_L1 10000
CH1_OFF_L1 CH2_OFF_L1 9900
CH1_ON_L2 CH2_ON_L2 1000
CH1_OFF_L2 CH2_OFF_L2 1010
The status of the limits is available as part of the status information State of the component type.
The Justified status indicator is always active. It indicates that the simulated scale is always
calibrated.
Symbol
Function
The FM 350-1 function module is a fast counter module for use in the S7-300 automation
system or as a module in an ET 200M station. Only distributed modules used on PROFIBUS/
PROFINET can be simulated with SIMIT.
The module has the following operating modes:
● Counting modes
– Continuous counting
– Single counting
– Periodic counting
● Measurement modes
– Frequency measurement
– RPM measurement
– Continuous periodic measurement
All required functions of these operating modes are simulated in SIMIT.
The data of the real FM350-1 are cyclically transmitted via PROFIBUS DP. The
acknowledgment principle was adopted in the SIMIT component.
You can find additional information in the "S7-300; Counter Module FM 350-1" documentation.
Some functions will not be discussed here in detail. We will merely point out the differences and
describe the basic behavior of the simulated component.
Note
Hardware interrupts are not supported by the simulated module.
Data reading via DS0/1 (diagnostic data record) is not supported in the simulated module.
Isochronous mode is not supported in the simulated module. In other words, synchronization
of the function module via PROFIBUS cannot be implemented due to the separation between
physical replication of the bus by the SIMIT Unit and simulation of the logic in this simulation
component.
Counting modes
In the counting modes, the measured value is calculated by adding up the pulses queued at
input X. With very slow counts or individual edges, it is possible to increment the counter by one
at the "TriggerUP" input with a positive edge or to decrement it at the "TriggerDN" input. This
makes it possible to simulate very high frequencies of counting pulses, but also to enable the
counting of individual pulses.
Count limits
The following applies for the 31-bit counting range:
● The high count limit is set at +2 147 483 647 (231 –1).
● The lower count limit is set at –2 147 483 648 (–231).
The following applies for the 32-bit counting range:
● The high count limit is set at +4 294 967 295 (232 –1).
● The lower count limit is set at 0 (zero).
Continuous counting
In this mode, the simulated FM 350-1 counts continuously starting at the count:
● When the counter reaches the upper count limit while counting forward and an additional
count pulse occurs, it jumps to the lower count limit and resumes counting there without
skipping a pulse.
● When the counter reaches the lower count limit while counting backwards and an additional
count pulse occurs, it jumps to the upper count limit and resumes counting there without
skipping a pulse.
One-time counting
By reaching the configured count limit in the main counting direction, the gate automatically
closes internally and it can only be started again by a new gate start.
Periodic counting
By reaching the configured count limit in the main counting direction, there is an internal jump
to the load value and counting resumes there.
Measurement modes
The measured value is applied directly at the "CNT" input with the measurement modes. The
measured value is equal to the counter value in these modes. Again, the count value can be
changed by 1 by positive edges at the "TriggerUP"/"TriggerDN" inputs.
The update time plays no role in the simulated counter module. The pending value is
transmitted to the controller via the feedback interface. Limit monitoring and gate control are
implemented.
Frequency measurement
The measured frequency is equal to the value applied at the "CNT" input.
Note
The value of the real FM350-1 is transferred here in the unit 10–3 Hz and must be specified
accordingly in the simulation.
Speed measurement
The measured speed is equal to the value applied at the "CNT" input.
Note
The value of the real FM350-1 is transferred here in the unit 10–3 /min and must be specified
accordingly in the simulation.
Note
The value of the real FM350-1 is transferred here in the unit 1µs or 1/16µs and must be
specified accordingly in the simulation.
You can find additional information on counting mode and measurement mode in the "S7-300;
Counter Module FM 350-1" documentation.
The "Reset" button can be used to manually reset the counter module. Then a restart
calibration must be performed.
You can find additional information in the "S7-300; Counter Module FM 350-1" documentation.
These parameters need to be adjusted for the respective FM350-1 instance. No automatic
import from HW Config is performed.
The individual parameters and your selection options from the drop-down lists are described in
the following sections.
"OperatingMode" parameter
This parameter determines the operating mode. The same value must be set as in HW Config
in STEP 7.
You can select the following functions from the drop-down list:
● Continuous counting
● Single counting
● Periodic counting
● Frequency measurement
● RPM measurement
● Continuous periodic measurement
"GateControl" parameter
This parameter determines the gate control of the counter module. Gate control is used to start
and stop the counting operations.
You can select the following functions from the drop-down list:
● "None": Gate is always open
● "SW gate": Gate state depends on the "SW_GATE" signal of the control interface
● "HW gate (level controlled)": Gate state depends on the "DI_Start" input (level controlled)
● "HW gate (edge controlled)": A positive edge at the "DI_Start" input opens the gate; a
positive edge at the "DI_Stop" input closes it
● "Latch": Requirement for saving counts
● "Latch/Retrigger": Requirement for saving counts followed by setting to the load value and
counting resumes starting at the load value
"CountRange" parameter
This parameter sets the count range. If the counter module is operating in measurement mode,
this setting has no effect.
You can select the following count ranges from the drop-down list:
● "0 to +32 bits"
● "−31 to +31 bits"
This setting has an effect on the count limits and signs of the transferred values.
"MainCountingDirection" parameter
This parameter determines the main counting direction. The main counting direction is only
relevant in the counting modes.
You can select the following functions from the drop-down list:
● "None": No counting direction is specified
● "Forward": Count up
● "Backward": Count down
"Latch" parameter
This parameter sets the requirement for saving the counts.
● "pos. edge": The count is stored with a positive edge at the "DI Start" input
● "neg. edge": The count is stored with a negative edge at the "DI Start" input
● "both edge": The count is stored with a positive or negative edge at the "DI Start" input
"SetCounter" parameter
This parameter sets the behavior for setting to the load value once or multiple times.
● "Single"
● "Multiple"
"GateFunction" parameter
This parameter sets the gate control to "Cancel" or "Interrupt".
● "Cancel"
● "Interrupt"
DP-DP-ID
Symbol
Function
The DP-DP-ID component type is used for simulation of fail-safe master-master
communication (Profisafe V1) with SIMIT and SIMIT Unit. The counterpart of a real
F_SENDDP/F_RCVDP block with SIMIT and SIMIT Unit configured in the CPU is simulated.
The SIMIT UNIT PROFIBUS or PROFINET simulates the configured DP/DP coupler or PN/PN
coupler with the respective universal modules. The fail-safe communication is simulated over
the user data of the module.
Import of the hardware in SIMIT is the same as in a standard project. The only thing that must
be taken into consideration in the HW Config of the S7 project is that the universal modules in
the DP/DP coupler or PN/PN coupler have the correct length for the fail-safe communication
blocks.
NOTICE
In case the connection is interrupted (for example by plugging the PROFIBUS cable), the CPU
must be restarted for the reintegration. Otherwise, it does not reset its internal telegram
counters.
Inputs
Unit
A module is connected at the Unit input via a Unit connector. The DP-DP-ID component type
enters the DP-DP-ID in one of the data records of the module connected at the Unit input.
DP_DP_ID
The DP-DP-ID is a system-wide, unique connection ID. This parameter must be identical to the
parameter of the same name of the partner block in the CPU.
Example
Figure 8-1 Hardware configuration: Slot 1 of the device 56 in the PROFINET is highlighted
Figure 8-3 DP-DP-ID component in SIMIT: Slot 1 of the device 56 in the PROFINET is connected to the
Unit input via the Unit connector. The same value, 10, is entered at the DP_DP_ID input as
in the F_RCVDP.
Multi HART
Symbol
Figure 8-4 Symbol for the Multi HART 8 component type (left) and the Multi HART 16 component type
(right)
Function
The Multi HART 8 and Multi HART 16 component types are multiplexers for the ET200SP HA
hardware family.
Depending on the value of the selection input Control, the component type Multi HART 8 / Multi
HART 16 switches one of the 32 / 64 inputs to the Value output. The Status output receives the
same value as the Control selection input.
The default value of the selection input Control is 0. All other inputs are set to 0.0 by default.
Parameter assignment
The configuration of the HART secondary variables in ET 200SP HA defines how many
selection inputs you need to connect in SIMIT:
● Configuration as "1 multiHART":
Example
The Multi HART component is used for the simulation of HART secondary variables when the
HART secondary variables in ET200SP HA are configured as "1 multiHART" or "4 multiHART"
and the Pcs7HaAI block is used in the PCS 7 project. The Multi HART component is not
required for "8 HART" configuration, since the secondary variables are available directly via the
process image.
In the following example, the four HART secondary variables are read from channel 2 of module
7.
As described in the help for ET200SP HA, the control byte for AB886 and the status byte for
EB546 is included in this configuration. AB886 is linked to the Control input of the Multi HART
component and determines the HART secondary variable to be currently read. The HART
secondary variable just read is passed to ED547.
In the example, control is generated by Pcs7HaAI and the following sequence is executed:
Control = Channel1_1. Then Status = Channel1_1 and Value = 1.0.
Control = Channel1_2. Then Status = Channel1_2 and Value = 2.0.
Control = Channel1_3. Then Status = Channel1_3 and Value = 3.0.
Control = Channel1_4. Then Status = Channel1_4 and Value = 4.0.
The configuration in CFC looks like this:
Symbol
Function
The ReadMemory component type enables one or more successive bytes from the bit memory
address area of a controller to be read. Enter the address of the first byte to be read at the
input MB. The read operation is executed when a rising edge occurs at the Trigger input, which
means a change from False to True.
The number N of outputs can be varied. It can be changed by "graphically scaling" the
component on a chart. You can specify a maximum of 32 outputs, which means you can read
a maximum of 32 bytes with a component of this type. The bytes that are read are available at
the outputs Y1 to YN.
Exactly one read operation is triggered while the simulation is being initialized. This means
initial values from the bit memory address area are available after initialization even though no
trigger signals have been sent.
The component can be operated with the following couplings:
● PLCSIM
● PRODAVE
● Virtual Controller
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The WriteMemory component type allows you to write to one or more successive bytes in the
bit memory address area of a controller. Enter the address of the first byte to be written to at the
input MB. The write operation is executed when a rising edge occurs at the Trigger input, which
means a change from False to True.
The number N of inputs can be varied. It can be changed by "graphically scaling" the
component on a chart. You can specify a maximum of 32 inputs, which means you can write to
a maximum of 32 bytes in the bit memory address area with a component of this type. The bytes
to be written are to be provided at inputs X1 to XN.
Exactly one write operation is triggered while the simulation is being initialized. Initial values can
therefore be written to the bit memory address area during the initialization process, even
though no trigger signals have been sent.
The component can be operated with the following couplings:
● PLCSIM
● PRODAVE
● Virtual Controller
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ReadDatablock component type enables one or more successive bytes from a data block
of a controller to be read. Enter the data block number at the DB input and the address of the
first byte to be read at the DBB input. The read operation is executed when a rising edge occurs
at the Trigger input, which means a change from False to True.
The number N of outputs can be varied. It can be changed by "graphically scaling" the
component on a chart. You can specify a maximum of 32 outputs, which means you can read
a maximum of 32 bytes with a component of this type. The bytes that are read are available at
the outputs Y1 to YN.
Exactly one read operation is triggered while the simulation is being initialized. Initial values
from the data block are available after initialization, even though no trigger signals have been
sent.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The WriteDatablock component allows you to write to one or more successive bytes in the data
block of a controller. Enter the data block number at the DB input and the address of the first
byte to be written at the DBB input. The write operation is executed when a rising edge occurs
at the Trigger input, which means a change from False to True.
The number N of inputs can be varied. It can be changed by "graphically scaling" the
component on a chart. You can specify a maximum of 32 inputs, which means you can write to
a maximum of 32 bytes in the data block with a component of this type. The bytes to be written
are to be provided at inputs X1 to XN.
Exactly one write operation is triggered while the simulation is being initialized. Initial values can
therefore be written to the data block during the initialization process, even though no trigger
signals have been sent.
The component can be operated with the following couplings:
● PLCSIM
● PRODAVE
● Virtual Controller
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The component type ReadDataReord allows a data record written by the controller or by SIMIT
VC to be read. Specify the number of the data record to be read at input DR. The read operation
is executed when a rising edge occurs at the Trigger input, which means a change from False
to True.
The number N of outputs can be varied. It can be changed by "graphically scaling" the
component on a chart. You can set a maximum of 64 outputs, which means that you can read
a maximum of 64 bytes with a component of this type. The bytes that are read are available at
the outputs Y1 to YN.
Exactly one read operation is triggered while the simulation is being initialized. This means
initial values from the bit memory address area are available after initialization even though no
trigger signals have been sent.
The component can be operated with the following couplings:
● SIMIT Unit
● Virtual Controller
● PLCSIM Advanced
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The component type WriteDataRecord allows a data record that can be read by the controller
or by SIMIT VC to be written. A validity check for the data record is not carried out. Specify the
number of the data record at input DR and the length of the data record at input Length. The
write operation is executed when a rising edge occurs at the Trigger input, which means a
change from False to True. If you only want to write a data record once when starting the
simulation, set the Trigger input to True.
The number N of inputs can be varied. It can be changed by "graphically scaling" the
component on a chart. You can set a maximum of 64 inputs and write a maximum of one data
record with a length of 64 bytes with a component of this type. The bytes to be written are to be
provided at inputs X1 to XN.
Exactly one write operation is triggered while the simulation is being initialized. Initial values can
therefore be written to the data block during the initialization process, even though no trigger
signals have been sent.
The component can be operated with the following couplings:
● SIMIT Unit
● Virtual Controller
● PLCSIM Advanced
See also
Access to a data record or memory area (Page 188)
SetInterrupt
Symbol
Function
The component type SetInterrupt sets the hardware interrupts in the SIMIT Unit coupling during
the simulation.
The number of binary inputs is variable. It can be changed by "graphically scaling" the
component on a chart. You can specify a maximum of 64 inputs, which means with a
component of this type you can trigger a maximum of 64 hardware interrupts at a hardware
object of the SIMIT Unit coupling.
The INX input hereby corresponds to the alarm [X] specified in the coupling. With a rising edge
at INX, the corresponding alarm is triggered (incoming), and with a falling edge it is removed
again (outgoing). You use the corresponding signal of the hardware object from the SIMIT Unit
coupling as interrupt output.
Note
If you do not use this component, direct inputs are no longer possible in the coupling. Direct
inputs in the coupling are immediately overwritten by the model values.
See also
Simulation of alarms (Page 92)
A component type that enables the transfer of axis values from SINUMERIK to SIMIT can be
found in the basic library in the directory COMMUNICATION | SINUMERIK.
Symbol
Function
The ADAS component type is used for parameter assignment and preparation of axis values,
which are transferred to SIMIT via PROFIBUS DP from a SINUMERIK controller using the
ADAS software package.
Note
The ADAS software package is not part of the SIMIT product and needs to be purchased
separately.
To transfer axis values you need to insert the PROFIBUS slave ccADAS into the SINUMERIK
hardware configuration. The GSD file of the ccADAS slave can be found on the SIMIT
Installation CD in the folder Tools/ADAS.
This slave has 8 bytes each of input and output data for communication and an additional 4
bytes for each axis value.
All I/O data are configured as double words in the coupling and must be connected to the SIMIT
component (QA, QB, Q1 .. Qn or IA and IB):
The transferred axis values are available at the analog outputs TRACKi, i = 2, …, N of a
component of type ADAS. The number N of available channels can be specified by scaling the
component. A maximum of 28 channels can be specified. You can, for example, connect the
TRACKi outputs with the 3D viewer control in SIMIT to animate the 3D view of the machine with
current axis values.
Note
The number of transferred axis values is specified by assigning parameters to the ccADAS
slave. You should set the number in the ADAS component to the same value as defined in the
slave to use all channels within the component.
In case of communication failure the integer output Error provides information about the cause
of the error.
Error Cause
0 No error
1 No reply to configuration of Track 1
2 No reply to configuration of Track 2
..
28 No reply to configuration of Track 28
100 No reply to Reset command
101 No reply to Set Communication command
Parameters
The ADAS component has the parameter vectors AxisType and AxisNumber, which have as
many elements as the specified number of channels. This allows for each channel to specify
which axis of the SINUMERIK-NC is to be transferred and whether the axis moves linearly or
is an axis of rotation.
● AxisType
Depending on this parameter assignment, the axis values are provided in mm
(translational), angle degrees (rotatory grad) or radians (rotatory rad).
● AxisNumber
This parameter specifies which axis is to be transferred on the corresponding ADAS
channel.
The figure below shows the parameters together with their default values:
Note
Note that the parameter assignment will be effective only if the Config button in the operating
window or on the basic symbol is pressed to transfer the configuration to the SINUMERIK while
the simulation is running and the SINUMERIK controller is connected.
As an alternative, you may also specify these settings in the SINUMERIK machine data.
Additional parameters
The additional parameter TimeOut allows you to specify the period of time after which the
component will cancel communication with the SINUMERIK, if the command to transfer the
configuration receives no response from the SINUMERIK.
The figure below shows the additional parameter together with its default values:
Operating window
The transfer of the configuration to the SINUMERIK can be triggered in the operating window
of the ADAS component type by using the Config button. While transfer is in progress, the two
displays Ok and Fault are not active. Successful transfer is indicated by the green display Ok,
and failure is indicated by the red display Fault.
The same operating and display elements can be found on the basic symbol and provide the
same function.
8.1.7 Controls
Binary display
Symbol
Function
The Binary display control is used to display a binary value. The color and shape of the control
can be defined in the view properties.
You can select any color for the signal Off state (signal value zero) and On state (signal value
one). You can also toggle the shape of the control between Rectangular and Round in a drop-
down box.
You can change the size of the control as required using the width and height handles on the
selection frame. To change the size using the corner handles, hold down the <Shift> key and
the size of the control will increase or reduce proportionately.
Analog display
Symbol
Function
The Analog display control is used to display an analog or integer value in the form of a pointer
instrument. The Data type of the signal to be displayed can be toggled between Analog
and Integer in the general properties of the control.
Other settings for the analog display can be adapted individually in the view properties. The
figure below shows the property view with the default settings.
The range of values and the scale, labels and color can all be set as required:
● Value range
The value range is determined by the minimum and maximum values. If the value to be
displayed is outside the set range of values, the pointer of the analog display appears in red.
● Scale
Start angle and end angle identify the start and end of the scale. The start angle displays the
minimum value and the end angle the maximum value. The angle is defined as degrees
from the horizontal axis in counterclockwise direction. Scale division indicates the
subdivision for values on the scale. Scale values are displayed with the specified number
of decimal places.
① Angle
● Label
You can enter a text in the Label property box that will appear in the analog display with the
adjustable Font size.
● Color
The border, scale and texts are displayed in the adjustable, uniform foreground color. The
background color can also be set as the fill color for the control.
You can change the size and thus the round shape of the control as required using the width
and height handles on the selection frame. To change the size using the corner handles, hold
down the <Shift> key and the size of the control will increase or reduce proportionately.
Digital display
Symbol
Function
The Digital display control is used to display the value of an analog or integer signal. The Data
type of the signal to be displayed can be toggled between Analog and Integer in the general
properties of the control.
For analog signals you can set the font size and the number of decimal places to be displayed
in the View properties dialog.
For integer signals, you can set the Font size, the Display format and the Data width in the
property view.
Decimal numbers can be positive or negative. In hexadecimal notation negative numbers are
always represented as a two's complement. When converting to hexadecimal numbers you
need to specify how many bytes are to be included (1, 2, 4 or 8 bytes). As hexadecimal numbers
are displayed with a fixed number of characters, this setting also determines the number of
hexadecimal characters displayed (2, 4, 8 or 16 places).
In the Characters display format only the specified number of bytes are included, starting with
the least significant byte, resulting in a display of 1, 2, 4 or 8 characters. A character
corresponding to the coding of the (extended) ASCII code is displayed if it is a displayable
character.
Note
If the data width is set to less than 8, the actual value of an integer input variable might not be
displayed in some circumstances.
The data width does not affect the input of a value as the effective value is not limited. However,
the way the entered value is displayed will depend on the data width setting.
The figure below shows examples of the effect of different display formats and data widths:
GHFLPDOE\WHV
GHFLPDOE\WHV
GHFLPDOE\WHV
GHFLPDOE\WH
KH[DGHFLPDOE\WHV
KH[DGHFLPDOE\WHV
KH[DGHFLPDOE\WHV
KH[DGHFLPDOE\WH
FKDUDFWHUE\WHV
FKDUDFWHUE\WHV
FKDUDFWHUE\WHV
FKDUDFWHUE\WH
You can change the size of the symbol as required, and thus modify the set font size, using the
width and height handles on the selection frame. To change the size using the corner handles,
hold down the <Shift> key and the size of the control will increase or reduce proportionately.
Symbol
Function
The Bar graph display is used to display an analog or integer signal in the form of a bar graph.
The Data type of the signal to be displayed can be toggled between Analog and Integer in the
general properties of the control.
Other settings for the bar graph display can be adapted individually in the property view.
Pushbutton
Symbol
Function
The Pushbutton control is used to enter a binary signal.
The pushbutton can be defined as Normally Open or Normally Closed in the general properties.
The default setting is Normally Open.
To activate the pushbutton while the simulation is running, simply click the button. The figure
below shows the unpressed button (a) and the pressed button (b):
(a) (b)
As can be seen in the properties window of the figure below, you can specify a text for the
pushbutton that will appear on the button in the configured font size.
The handles on the button frame can be used to change the size and thus adjust the size of the
specified text, for example. The text is aligned centered in the button (both horizontally and
vertically).
Symbol
Function
The Pushbutton with image is used to enter a binary signal; images are used to represent the
button position.
The pushbutton can be defined as Normally Open or Normally Closed in the general properties.
The default setting is Normally Open.
To activate the pushbutton while the simulation is running, simply click the symbol. The size of
the symbol and thus the size of the sensitive area can be changed using handles on the
selection frame.
In the property view you can specify images that represent the unpressed (Off) and pressed
(On) pushbutton while the simulation is running. Click to open the dialog for selecting the
corresponding graphic files. Click to delete the selection.
The Adapt to image size check box is not selected by default. The selected images will then be
adapted to the size of the button, which means the width and height are scaled accordingly. If
the check box is selected, the size of the button is matched to the size of the graphic for Image
(not pressed).
Switch
Symbol
Function
The Switch is used to switch a binary signal.
The switch can be defined as Normally Open or Normally Closed in the Off or On position in the
general properties. It is set to Normally Open in the Off position by default. The selected position
takes effect as the Default when the simulation starts.
To activate the switch while the simulation is running, simply click the button. The closed switch
is represented by a dark-blue border. The table shows the switch as Normally Closed and
Normally Open with the default settings Off and On.
Off
Symbol
Function
The Switch with image is used to switch a binary signal; images are used to represent the
switch position.
The switch can be defined as Normally Open or Normally Closed in the Off or On position in the
general properties. It is set to Normally Open in the Off position by default. The selected position
takes effect as the Default when the simulation starts.
To activate the switch while the simulation is running, simply click the symbol. The size of the
symbol and thus the size of the sensitive area can be changed using handles on the selection
frame.
In the property view you can specify images that represent the two possible switch states - Off
and On - while the simulation is running. Click to open the dialog for selecting the
corresponding graphic files. Click to delete the selection.
The Adapt to image size check box is not selected by default. The selected images will then be
adapted to the size of the button, which means the width and height are scaled accordingly. If
the check box is selected, the size of the button is matched to the size of the graphic for Image
(off).
Step switch
Symbol
Function
The Step switch is used to step through the switching of an integer value. The numerical value
is increased or reduced by one every time it is switched.
The minimum and maximum values for the switched signal can be defined in the general
properties. The default is a ten-step switch with a value range from 0 to10 starting with the
switch value 0.
To activate the step switch while the simulation is running, simply click the top ( ) or bottom
( ) button. The switch value that is currently set is displayed in the symbol.
The size of the symbol and thus the size of the two buttons can be changed using handles on
the selection frame.
Symbol
Function
The Step switch with image is used to step through the switching of an integer value; images
are used to represent the switch position.
The switch value from which the step switch starts is set in the general properties. The default
setting is zero. The numerical value of the switched signal is increased or reduced by one every
time it is switched.
The number of switching steps is defined by the number of images. The images are set in the
view properties. They change for every step while the simulation is running in the order set in
the Images list.
Click to open the dialog for selecting the corresponding graphic files. The selected image is
added to the list. The order of the images can be changed by swapping an image with the
previous ( ) or subsequent ( ) image. Click to delete an image.
To activate the step switch while the simulation is running, simply click the symbol. The
Switchover is selected via the drop-down list.
In the "Up-Down" parameter setting, the value of the step switch is incremented when you click
in the top half of the control and decremented when you click in the bottom half.
Handles on the selection frame are used to change the size of the symbol.
The Adapt to image size check box is not selected by default. The images are then adapted to
the size of the button, which means the width and height are scaled accordingly. If the check
box is selected, the size of the button is matched to the size of the graphic for the first image.
Digital input
Symbol
Function
The Digital input is used to enter an analog or integer signal value in digital form.
The data type of the signal can be set to analog or integer in the general properties. The Default
signal value can also be set. It is set to zero by default.
For analog signals you can set the Font size and the number of Decimal places to be displayed
in the View properties.
For integer signals, you can set the Font size, the Display format and the Data width in the
property view.
Entries must be made in the specified display format. If the syntax used does not correspond
to the specified display format, the input is interpreted as zero.
Decimal numbers can be positive or negative. In hexadecimal notation negative numbers are
always represented as a two's complement. When converting to hexadecimal numbers you
need to specify how many bytes are to be included (1, 2, 4 or 8 bytes). As hexadecimal numbers
are displayed with a fixed number of characters, this setting also determines the number of
hexadecimal characters displayed (2, 4, 8 or 16 places).
In the Characters display format only the specified number of bytes are included, starting with
the least significant byte, resulting in a display of 1, 2, 4 or 8 characters. A character
corresponding to the coding of the (extended) ASCII code is displayed if it is a displayable
character.
The data width does not affect the input of a value because the effective value is not limited. The
specified value is only displayed in accordance with the configured data width.
Note
If the data width is set to less than 8, the actual value of an integer input variable might not be
displayed in some circumstances.
When entering values via the Digital Input control, you must use the specified display format.
If the entry is syntactically incorrect, it is interpreted as "0".
The figure below shows examples of the effect of different display formats and data widths:
GHFLPDOE\WHV
GHFLPDOE\WHV
GHFLPDOE\WHV
GHFLPDOE\WH
KH[DGHFLPDOE\WHV
KH[DGHFLPDOE\WHV
KH[DGHFLPDOE\WHV
KH[DGHFLPDOE\WH
FKDUDFWHUE\WHV
FKDUDFWHUE\WHV
FKDUDFWHUE\WHV
FKDUDFWHUE\WH
You can change the size of the symbol as required, and thus modify the set font size, using the
width and height handles on the selection frame. To change the size using the corner handles,
hold down the <Shift> key and the size of the control will increase or reduce proportionately.
The signal values appear right-justified in the symbol while the simulation is running.
Slider
Symbol
Function
The Slider is used to set an analog or integer signal.
The default setting for the signal value is set in the general properties. The default is zero.
The slider is moved with the mouse while the simulation is running. Position the mouse pointer
over the button of the slider, hold down the left mouse button and move the button to the desired
position. You can also click to the right or left of the button to increase or reduce the set value
by one step.
Other settings for the slider view can be changed individually in the property view.
● Scale
The scale is determined by the initial value, the end value and the increment.
● Orientation
The possible orientations for the control are Horizontal and Vertical.
The following properties can be set:
Signal splitter
Symbol
Function
The Signal splitter is used to force, which means to set, values at the inputs and outputs of
components or coupling signals while the simulation is running using any of the Input controls.
Forcing is already available in the property view for all inputs and outputs of components.
The Signal splitter control also allows you to force inputs and outputs using any Input control,
as described below by way of example.
Tip: You can use the signal splitter without an assigned Input control and connect it, for
example, to the component input or component output that is to be forced. In this case, the
signal splitter will perform the same function as the signal splitter in the properties of the input
or output.
The figure below shows a section from a chart containing an adder whose output is connected
to the inputs of two PTn elements.
If you want to implement the forcing of the adder output and the two inputs of the PTn elements
using sliders, add a slider and a signal splitter to a chart for each input and output to be forced.
Then open the property view for the first slider, set its connector to invisible and enter the output
of the adder as the connected signal. Then open the connector properties for the associated
signal splitter. Its connector is always invisible, as can be seen in the figure below.
Here, too, you enter the adder output as the signal.
Connect the other two sliders and signal splitters to the inputs of the two PTn elements in the
same way. You can now force the output and the inputs while the simulation is running, as
shown by way of example in the figure below.
The signal splitters for the two controls Slider#1 and Slider#2 are switched on ( ). Forcing of
the adder output and of the input to PTn#1 via the two sliders is thus activated. The signal
splitter for Slider#3 is not switched on ( ), which means the input PTn#3 cannot be forced this
way. Slider#3 is shown as disabled and is also marked with the overlay .
Values for the output and input can now be set using the first two sliders. In the example, the
adder output is set to the value 25 and the input of PTn#1 is set to the value 40. The input of
PTn#2 is connected to the adder output, and thus takes on its value (25). The (inactive)
Slider#3 displays the value of the input connected to it.
The following points should thus be noted when using signal splitters:
● The signal splitter and the associated Input control should be linked to the input or output to
be forced.
● Forcing is not activated for signal splitters that are not switched on. The associated input
control is shown as disabled and is marked with the overlay . It indicates the value of the
connected input or output.
● Switching on the signal splitter activates forcing.
See also
Properties of the inputs (Page 383)
Properties of the outputs (Page 385)
Action
Symbol
Function
This action opens a chart or a trend.
You can set whether a chart or a trend is to be opened under "Action" In the general properties.
As "Target", enter the chart or trend to be opened starting with a slash followed by the complete
folder hierarchy separated by slashes. Alternatively, you can drag-and-drop the required chart
or trend from the project tree to the "Target" property field.
The size of the button can be changed and adjusted, for example to adjust it to the size of the
specified text. The text is aligned centered in the button (both horizontally and vertically).
The graphical editor in SIMIT allows you to clearly visualize the behavior of a machine using
simple graphical basic elements. Two-dimensional graphics can be used to draw a machine
and to show movements of the machine by animating relevant parts of this drawing. The 3D
Viewer control gives you the added option of incorporating three-dimensional animated views
of a machine in your simulation. The representation of the machine is then clearer, and the
movements of the machine are displayed more realistically.
In order to use the 3D Viewer control you must have a three-dimensional geometry model of the
machine. This 3D model must be made kinematic, which means it must be designed in such a
way that it can be linked to signals from the functional simulation and then execute the
animations controlled by these signals in the simulation. The kinematic 3D model includes
elements that are evaluated by the 3D Viewer control and converted into animations of the 3D
model.
Like the other controls in the basic library, the 3D Viewer control is inserted in a chart and its
parameters are assigned accordingly. It also has connectors with which it can be connected to
signals of the functional model. A special feature of the 3D Viewer control is a menu that can
be used to adapt the view of 3D model by means of commands.
Animation sensors
A 3D model usually uses sensors to respond to user actions. Sensors in the 3D Viewer control,
on the other hand, are routed to connectors. This means you can connect the connectors of the
3D Viewer control to signals from your functional model. This means movements are calculated
by the functional model during the simulation and visualized by the 3D Viewer control.
The 3D Viewer control supports the following sensors for animating the 3D model:
● Plane sensors for the translational movement of objects
● Cylinder sensors for rotating objects about the local coordinate axes
● Sphere sensors for rotating objects around a vector
For each motion sensor of the 3D model the following applies:
● At least one higher-level Transform node must exist for a sensor. The sensor can be placed
anywhere in the Transform node.
● The position of the sensor alone determines which shapes or shape groups are moved: The
Transform node to which the sensor is assigned and all its child nodes are moved by the
sensor.
● Routes to sensors are not necessary and are not evaluated.
For each sensor a specific number of connectors is made available in the connector properties
of the control. Connect the connectors that perform the desired movement in the 3D model to
the corresponding signals in your functional model.
Faulty sensors, which means sensors that are not assigned to a Transform node, are
interpreted as not being present. For this reason no animation connectors are available for
faulty sensors in the 3D Viewer control properties.
Once this VRML file has been loaded into the 3D Viewer control, the following three analog
connectors are available in the 3D Viewer control properties for translating the cone:
Once the VRML file has been loaded into the 3D Viewer control, there are three analog
connectors available for a cylinder sensor in the control properties:
Once this VRML file has been loaded into the 3D Viewer control, the following three analog
connectors for rotating the cone are available in the 3D Viewer control properties:
Once this VRML file has been loaded into the 3D Viewer control, the following four analog
connectors for rotating the cone are available in the 3D Viewer control properties:
Scaling objects
If you wish to scale the size of an object, which means a shape or shape group, you need to
modify the name of the Transform node to which the object is assigned or the Transform node
containing the object to be scaled: Prefix the name of the Transform node with the
identifier SCALE. Negative scale values flip the object in the scaling axis.
Note
A scale value of zero in two degrees of freedom, which means in two directions, will cause the
object to disappear from the animation.
Once the VRML file has been loaded into the 3D Viewer control, there are three analog
connectors available for a scaled Transform node in the control properties:
Once this VRML file has been loaded into the 3D Viewer control, the following three analog
connectors for scaling the box are available in the 3D Viewer control properties:
Once this VRML file has been loaded into the 3D Viewer control, the following four analog
connectors for the transparency and color of the cylinder are available in the 3D Viewer control
properties:
Note
An invisible shape remains invisible even if you change the color values. Only changing the
transparency value makes it visible again.
To make an entire group of shapes invisible, move the group to a new transformation node and
scale the node in two axis directions to zero or one. You can find additional information on this
in section: Scaling objects (Page 577).
If you want to assign the same color to several shapes and animate it, you can utilize the
inheritance of properties. The material property of a primary shape can be passed onto any
number of other shapes. The primary shape includes the RGBT identifier in its name. The
resulting four connectors of the primary shape can be used to switch the color (and also the
visibility/transparency) of all other shapes that inherit this material property.
This is illustrated by the example below: Two cylinders change color at the same time, but only
one has the RGBT identifier.
Switching viewpoints
If viewpoints are included in a VRML file, they can be switched both dynamically in the
simulation and also by manual operation of the 3D Viewer control. If a VRML file is loaded into
the 3D Viewer control, the integer VIEWPOINT connector appears in the connector properties
of the 3D Viewer control, provided that viewpoints have been defined in the file.
The VIEWPOINT connector can be set in the value range 1, ..., N, whereby N is the number of
defined viewpoints.
The example below shows the syntax for two viewpoints called Main View and Front View:
To switch viewpoints, connect the VIEWPOINT connector to an integer signal whose values
you can use to switch to the corresponding viewpoint.
You can use the Operable property to operate the 3D viewer control (even when the simulation
is stopped) and set the view of the 3D model. You can find more information about this in the
section: Simulating with the 3D Viewer control (Page 582).
The scene settings (camera settings) are saved with the chart and are restored when you open
the chart.
The connectors that can be used for translating, rotating, scaling, hiding or changing the color
of shapes are all provided with a button. Clicking this button starts an explanatory animation
for this connector, making it easy to identify the animated object or its movement axis in the 3D
scene. Then link the connectors that execute the animations you require to the corresponding
signals of the "Signals" task card using drag-and-drop.
Note
Of the connectors of a sphere sensor, only connector #R, which is used to animate the angle
of rotation, has an animation button . When this animation button is activated, a rotation of
the object about the X-axis is animated.
You can reset the center of rotation/viewpoint by double-clicking an element of the scene.
The view cube in the bottom right corner of the 3D Viewer control shows you the current viewing
direction of the 3D scene. Click one side of the cube to reset the scene to the corresponding
viewing plane. Double-click to set the opposite viewing plane. You can show and hide the view
cube by going to "View > Show view cube".
You can also use the shortcut keys listed in the table below to switch the viewing plane.
The bottom left corner of the 3D Viewer control shows the coordinate system with the three
axes X, Y and Z. You can show and hide this coordinate system by going to "View > Show
coordinate system" (see figure above).
Note
The viewing planes are defined in the VRML specification: a Cartesian, left-handed, three-
dimensional coordinate system is used in which the positive Y-axis points upwards and the
viewer looks from the positive Z-axis towards the negative Z-axis.
When you create the 3D model or export it to a VRML file, make sure that the Y axis is pointing
upwards in accordance with the VRML specification.
You can alter the response to rotation with the mouse or arrow keys by going to "Camera >
Rotation sensitivity" and "Camera > Inertia". The sensitivity and inertia factor can be reduced
or increased by means of a slider. The default setting for both sliders is one.
8.2.1 Introduction
The FLOWNET and CHEM-BASIC libraries are extensions of SIMIT that provide component
types for creating simulations of pipeline networks. You use the component types of CHEM-
BASIC, in particular, to create simulations in the chemical and pharmaceutical industries.
By connecting components of these libraries, a model of a pipeline network – a flow network –
is created and can be used to simulate the thermodynamic processes in pipeline networks. The
FLOWNET and CHEM-BASIC libraries enable use of a special solution method in SIMIT that
calculates the flow rates, pressures and specific enthalpies during simulation of pipeline
networks.
With CHEM-BASIC the material mixtures are modeled as pseudo ingredients with the
corresponding mixture properties (especially heat capacity and density). The individual
components of the flow networks can also be connected to models of the actuator-sensor level
(basic library).
Although a model approach based on the physical balance equations underlies the flow
networks in SIMIT, the goal is not to enable dynamic process simulations for the design of plant
components or plants. Rather, the goal is to provide a physically plausible simulation of the
thermodynamic variables in pipeline networks for virtual commissioning. This simulation should
be easy to create from components in a graphical interface and should be stable even in
extreme situations. Thus, when component types of the FLOWNET and CHEM-BASIC libraries
are implemented, a detailed simulation of the physics is not the focus. Rather, the emphasis is
on a simple parameter assignment of components and a stable behavior in the flow network.
The component types of the FLOWNET- and CHEM-BASIC libraries can be used to implement
flow networks for different media:
● water/steam,
● liquids or
● ideal gases.
With the Modul Component Type Editor (CTE) of SIMIT, you can create your own flow network
components and thus specifically expand your flow network library. The flow network solution
method can be employed using FLOWNET-specific connection types of the components.
However, existing component types of the CHEM-BASIC library cannot be modified by the
user.
Note
A check is made during startup of the simulation to determine whether your SIMIT installation
has a license for the FLOWNET- or CHEM-BASIC library. If flow network components are
present in your simulation project, that is, components that utilize the solution method for flow
networks, the simulation can only be started if you have the license for FLOWNET or CHEM-
BASIC.
Use the Topology connector to create a topological flownet connection between two or more
branch components. Two components are connected by the CON_A connector under (a) in the
figure below. The connection is functionally identical to the direct connection of both
components via a connecting line, as shown under (b) in the figure below:
Three components are connected by the NODE_A connector under (a) in the figure below. This
configuration is functionally identical to the connection using a connection node that is shown
under (b) in the figure below.
Operating principle
Certain components in the CHEM-BASIC library have an (additional) parameter for geodetic
height, geoHeight. The geodetic height specifies the height z of the equipment. Negative values
indicate lower components. The following formula is used to calculate the pressure change
resulting from geodetic pressure:
ΔPgeo = p • g • geoHeight
A distinction is drawn between the following situations as regards the effect of geodetic height
on the simulation:
● Components that only connect topologically connected flow.
Example: HeatExchangerGeneral. Connection of two topologically separate flow networks.
These flow networks exchange heat, but their pressure and mass flows are separate.
● Components that combine flows from flow networks that are not topologically connected.
Example: StorageTankLiquid. Flows from different flow networks are mixed. The internal
pressure in the tank is mapped to the various different flow networks and therefore
influences the mass flows.)
Components that only connect topologically connected flows operate with differential pressure
only. Geodetic height is not relevant in to this. For these components, the geodetic height is
relevant to material properties and internal functions, for example HeatExchangerGeneral:
Effect on the boiling point of water.
Components that combine flows from topologically separate flow networks work with absolute
pressures. The geodetic height therefore affects both the incoming and the outgoing flows. The
pressure in these nodes is increased by the geodetic height.
Example
A pump must build up additional differential pressure in order to pump a liquid to a tank that is
5 m higher. From that higher tank, the liquid then flows into a lower tank. A process tag is fitted
at a height of 2.5 m. All process tags show the pressure that would actually be measured there.
See also
Centrifuge (Page 645)
Compressor (Page 640)
Condenser (Page 613)
DrumWS – Storage tank for water/steam (Page 682)
ElectricHeatExchanger – Electrically heated heat exchanger (Page 618)
HeatExchangerGeneral (Page 619)
HeatExchangerShellTube – Shell and tube heat exchanger (Page 622)
Mixer (Page 637)
PipeMeasure – Pipe measuring point (Page 632)
Pump (Page 643)
PressureStrainer (Page 662)
Screening device (Page 671)
Separator (Page 673)
StorageTankLiquid – Storage tank for liquid media (Page 696)
8.2.4 Flownets
The flownet topology for configuring the flownet solution procedure is derived from the
interconnection of flownet components. While the simulation is running, the flownet solution
procedure and the flownet components exchange data: calculated values or flownet
parameters.
Flownets can be depicted by graphs, whose branches (edges) form the pipelines with their
fittings (valves, pumps, etc.), while their nodes form the pipe joints. The graph is directional,
which means the direction of a branch indicates the direction of flow. The graph is also
interconnected just like the flownet. The graph represents the topology of the flownet on the
level of pipelines and joints. As an example, the following figure shows a graph with 7 nodes Ki
and 9 branches Zi:
A graph, as shown in the following figure, with three branches and four nodes results from the
example in the section: Flownets (Page 590).
Nodes K1, K3 and K4 are used to set the boundary conditions for the flownet. For example, the
pressure on the connections of both tanks is specified with these external nodes. In contrast,
node K2 is an internal node, for which the relevant variables, such as pressure, are calculated
using the flownet solution procedure.
The solution procedure for flownets is based on determining the flow in the branches depending
on the pressure, using the momentum balance, and on balancing the flow of matter and
enthalpy in the nodes. The state variables for such a system therefore are the mass flows in the
branches and the pressures and specific enthalpies in the nodes. Other variables, such as
density and temperature in the flownet, can be derived according to the medium in question.
If the flownet components in a branch change neither the rate nor the enthalpy of flow in that
branch, the branch is removed from the flownet, which means both nodes are merged to form
one node.
The solution procedure for flownets is a cyclical solution procedure with equidistant time slices
that extends the standard solution procedure. Flownet component types can also be used in
addition to other component types, such as those in the basic library. Specific connections are
used for data exchange between flownet components and the flownet solution procedure.
Through these connections, the components receive values calculated by the flownet solution
procedure; these are then used to calculate variables that are sent back to the flownet solution
procedure.
Note
Depending on the structure of the flownet and on the parameter assignment of the flownet
components, the calculation of the flownet can become unstable during simulation and the
values of the flownet state variables can grow beyond all limits as a result. The stability of
flownets is not checked in SIMIT. In this case, you can establish stability by setting a smaller
value for the cycle time of the flownet, and/or by modifying the parameters of the flownet
balances.
Obviously a flownet must consist of at least one branch with two nodes. The following figure
shows the minimal graph.
The figure below shows a corresponding minimal flownet. The nodes can be external (as in the
figure) or internal.
If a branch is not completed with two nodes, as shown in the figure below, an error message is
output when you start the simulation and the simulation is not started.
The figure below shows this error message, "Isolated branch component(s)", and lists the
components in this branch.
A similar error message appears if the flownet only contains a single isolated component. The
corresponding graph then consists of only one branch or node and does not meet the minimum
requirements for a flownet.
The flownet components and the flownet solution procedure are also processed cyclically in
SIMIT. The flownet components must be assigned to a time slice for this purpose. All
components of a flownet must be assigned parameters with the same time slice. Otherwise the
simulation start is canceled with an error message as the one in the figure below.
density change is negligible for slight throttling, so it is acceptable to regard the density as
constant.
Thus only the pressures at the connection points need to be considered for branch objects. The
relationships between the pressures on either side of a branch object and the mass flow in the
branch, such as ˮ ෙS a P & , are purely of an algebraic nature.
Momentum balance is applied to each branch k using pressure forces. Friction forces,
acceleration forces and gravity are ignored. With a uniform cross-section Ak in a branch of
length Lk, the following applies
GP&N
/N $N ෙSN $N ෙSN ˧
GW ˧
where Δpk = pk,A – pk,B is the pressure difference over the entire branch k, and ΔpK,k = pK,kA – pK,kB
are the pressure differences of the individual branch elements (see the figure below).
%UDQFK %UDQFK
1RGH$ REMHFW REMHFW 1RGH%
SN$ SN$ SN% SN$ SN% SN%
P& N
GP&N $N ෙSN ෙS NJ
N˧
GW /N EDU ˧ EDU PV
The length and cross-section of a branch are generally unknown so a reasonable estimate
must be made. Assuming for example a cross-section of 0.05 m2 and a length of 10 m results
in a factor that is subsequently described as the momentum factor
$N
$N
/N
of 500 m.
The inflow and outflow of the medium are dynamically balanced at each node. Each node is
assigned a material balance envelope, which means a volume. The mass inflow and outflow
are balanced as well as the enthalpy inflow and outflow as a measure of the energy conversion.
GˮL
9L
GW P&
˧
˧
Vi is the volume of the material balance envelope assigned to the node, pi is the density of the
medium within the material balance envelope and the P & ˧ are the inflows and outflows. Inflows
are positive ( P˧ ! ), outflows are negative ( P˧ ).
& &
Using the equation of state ρ= ρ(p,h) and assuming an isenthalpic change of state for the
pressures in the node, the following applies:
GSL GˮL
GW
9
L GSL
P& ˧
K FRQVW ˧
The term
GˮL
9L
GSL
is a measure of the compressibility of the medium. Using the compressive modulus Ki
Gˮ
.L 0L 9L L
GSL
the following applies for the mass balance:
GSL .L
GW 0L
P&˧
˧ FL P
˧
&˧
The default setting for the specific compression module ci = Ki / Mi in the flownet solution
procedure is the same for all nodes in the flownet. However, various factors result in increased
compressibility ci of gases and steam in contrast to liquids, and this is taken into consideration
for media with higher and lower densities. You can find additional information on this in section:
Parameter assignment of flownets (Page 597).
G KL 0 L
GW
K P& ˧
˧ ˧
where Mi is the mass and hi is the specific enthalpy of the medium within the material balance
envelope. It follows from
GK L
GW 0L
P& K
˧ෛ = L
˧ ˧ KL
that by using the difference in enthalpy only the inflows to the node i (k ∈ Zi) need to be summed.
Just like the mass balance factors ci, the default thermal factors mi = 1 / Mi in the flownet solution
method are equal for all nodes, but have different values for media with higher and lower
densities.
Water/steam medium
In the case of water/steam, the density in the nodes is calculated using the equation of state for
water/steam with pressure p and specific enthalpy h:
ρ= ρ(p,h).
Liquid medium
In the case of liquids, calculation is based on constant density throughout the entire flownet.
The default is a density of 997.337 kg/m3.
Calculation
The gas equation pV = mRsT is used for ideal gas. Using the specific heat capacity cp the
density is given by
3D
S ຘ
P EDU
ˮ
9 K K
56 7
FS
with pressure p in bar, the specific heat capacity cp in kJ/kgK and the specific gas constant RS
in kJ/kgK. If the triple point of water is used for the zero point (T0, h0), we can set T0 = 273.15
K and h0 = 0. The density is then calculated using the following relationship
3D
S ຘ
ˮ EDU
K
56 .
FS
In the flownet solution procedure, the specific gas constant has a value of 0.287 kJ/kgK
(specific gas constant for dry air).
GK L
P & ˧ K ˧ KL F L 7L 7(QY
GW 0L ˧ෛ =
L
Where TEnv is the ambient temperature, Ti is the temperature of the node and
ci = αiAi
is the determining heat transfer factor, which is the product of the heat transfer coefficient αi and
the heat transfer surface Ai.
For calculation of the heat exchange with the environment, use the JointParam component as
the node.
The variables for the branches and nodes of a flow network are calculated with the help of the
above-described parameters. These parameters are preset with corresponding values in the
flow network solution method but can be changed using special component types of the
FLOWNET and CHEM-BASIC libraries.
Component types
You can use the following component types for parameter assignment of networks:
● NetParam for general parameter assignment of flownets in FLOWNET (NetParam –
network parameter assignment (Page 722)) and in CHEM-BASIC (NetParam – Network
parameter assignment (Page 676))
● NetWS for parameter assignment of networks with water/steam as the medium in
FLOWNET (NetWS – water/steam network parameter assignment (Page 731)),
● NetLiquid for parameter assignment of networks with liquids as the medium in FLOWNET
(NetLiquid – liquid network parameter assignment (Page 748)) and
● NetGas for parameter assignment of networks with ideal gas as the medium in FLOWNET
(NetGas – gas network parameter assignment (Page 761)).
You can use the following component types for specific parameter assignment of individual
nodes:
● JointParam for general parameter assignment of nodes in FLOWNET (JointParam –
parameterizable joint (Page 724)) and in CHEM-BASIC (JointParam – configurable
pipeline node (Page 608))
● JointParamWS for parameter assignment of a node in a network with water/steam as the
medium in FLOWNET (JointParamWS – water/steam parameterizable joint (Page 734)),
● JointParamLiquid for parameter assignment of a node in a network with liquid as the
medium in FLOWNET (JointParamLiquid – liquid parameterizable joint (Page 751)),
● JointParamGas for parameter assignment of a node in a network with ideal gas as the
medium in FLOWNET (JointParamGas – parameterizable joint (Page 764)),
You can use the following component type for parameter assignment of individual branches:
● BranchParam in FLOWNET (BranchParam – branch parameter assignment (Page 723))
and in CHEM-BASIC (BranchParam – Branch parameter assignment (Page 675))
Connection types
The following sections describe the connection types with which you can use parameter
assignments in your self-created flow network components in FLOWNET:
● Connector type FLN5 for parameters of a flownet (Page 781)
● Connector type FLN6 for parameter assignment of a branch (Page 782)
● Connector type FLN7 for parameter assignment of an internal node (Page 782)
Flownet media
The following media can be specified for a flownet:
● water/steam,
● ideal gas or
● liquid
Water/steam is the default medium.
ʿ
ʿ
N ˧
Node parameters
The following variables can be parameterized for nodes in a flownet:
● Specific compression modulus c = K / M
● Thermal factor m = 1 / M
Both variables can be individually specified for water and steam as well as liquid and gas.
Transitions between the parameters cL and mL and the parameters cG and mG for water/steam
medium are calculated by the flownet solution method based on the density according to the
following scheme:
and
The transition between both parameter values can also be set with a linear transition function:
F/ IRU ˮ ! ˮ/
F IRU ˮ ˮ*
F *
ˮ* ˮ/ ˮ
F F F RWKHUZLVH
/ * /
ˮ ˮ/ ˮ *
and
P/ IRU ˮ ! ˮ/
P IRU ˮ ˮ*
P *
P* P /
P/ Y Y/ RWKHUZLVH
Y* Y/
Initialization of variables
Each time the simulation is started, the flownet state variables are initialized as follows:
All branch mass flow rates are initialized with a value of zero ( P
& ). This initialization cannot
be changed. The default values for the pressures in the nodes are p = 1 bar, but they can be
changed to other values by means of a parameter. The initial value h for the specific enthalpy
depends on the medium in the flownet as follows:
● h = 100 kJ/kg for water/steam,
● h = 83.6 kJ/kg for liquid and
● h = 20 kJ/kg for ideal gas.
These initial values can be changed by means of a parameter.
Parameter overview
The table below provides an overview of the available flownet parameters. The signal column
lists the names of the input or output signals for the component, the designation column gives
the names under which the parameters can be found in the component properties dialog. The
default values and units are shown in the last column. If explicit parameters are not set, the
defaults for the flownet as described above apply.
$FWXDWRUVHQVRUOHYHO
3RVLWLRQ 3K\VLFDOPHDVXUHG
YDOXH
6LPXODWLRQOHYHO
Figure 8-5 Schematic coupling of the actuator/sensor level to the simulation level
The following options are available to link the simulation level to the actuator/sensor level:
● Direct connection over signal lines (only possible when the actuator/sensor level and the
simulation level are implemented in one chart)
● Connection of components over signal lines using global connectors
● Implicit connection of the actuator/sensor level to the simulation level
$FWXDWRUVHQVRUOHYHO
6LPXODWLRQOHYHO
Figure 8-7 Coupling the actuator/sensor level to the simulation level by means of signal lines and
connectors
To support the type of coupling for pumps and valves, the input Position is given a default. This
default is defined as follows:
In case of an implicit coupling of measuring points, the corresponding reading blocks in the
actuator/sensor level must be initialized using templates.
8.2.5.1 Burner
Symbol
The component calculates the energy released during combustion and provides it at output Q.
This combustion energy can be used to heat the content stored in other components (e.g.
Storage TankLiquid or PressureStrainer).
Function
The Burner component is connected to a flow network over the connectors A and B.
If the fuel is ignited (by means of the input Ignation or the "Ignition" button in the operating
window), the heat flow released from complete combustion of the fuel is output at the output Q.
The heat flow is calculated based on the specified heating value and the mass flow. Typical
heating values are:
Parameters
Additional parameters
8.2.5.2 Fittings
ChangeCrossSection
Symbol
Function
The ChangeCrossSection component calculates the pressure loss in a pipe with a change of
cross section. The component is configured on the basis of diameter 1 at connection end D1
and diameter 2 at connection end D2.
A constant change in cross section with an angle of 4° is assumed for pressure loss
calculations. The component therefore operates either as a nozzle (diameter 1 > diameter 2)
or as a diffuser (diameter 1 < diameter 2) depending on the dimensions.
Display
The symbol changes accordingly (direction of flow from D1 to D2).
Nozzle Diffuser
Parameter
Operating window
The following variables are displayed in the operating window:
Nozzle
Symbol
Function
The Nozzle component type is used to simulate the pressure drop of a connection pipe due to
a change in cross section or inlet effects at devices. You can uses this type for connection of
pipelines to the following component types:
● Tanks
● Heat exchanger
● Centrifuge
● Separator
In principle, you can also connect pipelines to the named components without the Nozzle
component type. However, it gives you the option of configuring the pressure drop of the
connection pipe using the Kvs parameter.
The pressure drop calculated in the Nozzle component type depends on:
● Size of the nozzle (kVS value)
● Throughflow (volume flow, medium)
The pressure drop across the nozzle is calculated according to the following formula.
ෙS P& VHF
EDU NJ K
N96 ˮ
P
Whereby:
Parameters
Connection example
Symbol
Function
You can use component type Joint to join the three branches connected to its connectors A, B
and C in a node. An internal node is added to the flow network with the component Joint.
The parameters required for parameter assignment of this node are read from the
corresponding NetParam block of the flow network. As a result, all nodes of this type located in
the same flow network have the same parameter assignment.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
You can use component type JointParam to join the three branches connected to its
connectors A, B and C in a node. An internal node is added to the flow network with the
component JointParam. Unlike with the component type Joint, each instance of the component
type JointParam is configured individually.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Orifice
Symbol
Function
The Orifice component calculates the pressure loss of an orifice in a pipe. The component is
configured on the basis of the diameter of the pipe DiameterPipe and the diameter of the
orifice DiameterOrifice.
Parameter
Operating window
The following variables are displayed in the operating window:
Pipe
Symbol
Function
The Pipe component calculates the pressure loss in a pipe. The pipe is configured on the basis
of the pipe length l, the pipe diameter d, the number of elbows n, the ratio of the bend radius to
the pipe diameter, and the roughness k. Pressure loss largely depends on the Reynolds
number Re, so you also need to specify the viscosity η of the medium.
Note
The density is only calculated once for each component. Density is therefore calculated as
constant throughout the entire section of pipe. If you want to take account of a change in
density, you will need to divide up the pipe and connect the components one at a time.
Pipe elbows are always assumed to have a 90° bend. If the ratio of bend radius to pipe diameter
RatioRD is greater than 10, elbows are treated like straight pipe. They therefore increase the
length of the pipe Length.
Parameter
Operating window
The following variables are displayed in the operating window:
8.2.5.3 Graphics
Membrane
Symbol
Function
The Membrane component has no function and is used only for graphic display purposes.
Motor
Symbol
Function
The Motor component has no function and is used only for graphic display purposes.
MotorThreePhase
Symbol
Function
The MotorThreePhase component has no function and is used only for graphic display
purposes.
8.2.5.4 Heatexchanger
Condenser
Symbol
Function
The Condenser component is a model of a heat exchanger with which the connected flow can
be (partially) condensed on the warm side (HIn, HOut). The heat required for condensing is
withdrawn from the flow on the cold side (CIn, COut). The composition of the warm flow
(component of the low boiler) is specified over the z_in input. The vapor fraction (vf =
VaporFraction) as well as the composition in the liquid (x_out) and in the gas phase (y_out) is
calculated and then made available at the output.
The capacitor is parameterized via the heat exchange surface A and the heat transfer
coefficient k. The mixture to be vaporized is defined over the boiling temperature of the low and
high boiler (TS_LB, TS_HB) as well as over the vaporization enthalpies (hv_LB, hv_HB). The
size of the boiling lens can be varied using the S parameter. This means:
● S = 0, maximum size of the boiling lens (see figure)
● S = THB − TLB, no boiling lens (makes no sense physically)
7HPSHUDWXUH>r&@
7HPSHUDWXUH>r&@
0DVVIUDFWLRQKLJKERLOHU 0DVVIUDFWLRQKLJKERLOHU 0DVVIUDFWLRQKLJKERLOHU
>NJNJ@ >NJNJ@ >NJNJ@
Tau line
Boiling point curve
Figure 8-18 Boiling lens as a function of the parameter S (spread)
NOTICE
The flow direction is permanently set on the warm side. A flow is always only possible from the
input (HIn) to the output (HOut). A flow due to a difference in pressure from the output to the
input is prevented by a modeled check valve.
The flow direction is permanently set on the cold side. A flow is always only possible from the
input (CIn) to the output (COut). A flow due to a difference in pressure from the output to the
input is prevented by a modeled check valve.
A flownet with the medium Ideal gas must be connected at the input on the warm side (HIn).
A flownet with the medium Liquid must be connected at the output on the warm side (HOut).
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
See also
Geodetic height (Page 588)
Evaporator
Symbol
Function
The Evaporator component is a model of a heat exchanger with which the connected flow can
be (partially) vaporized on the cold side (CIn, COut). The heat required for vaporizing is
withdrawn from the flow on the warm side (HIn, HOut). The composition of the cold flow
(component of the low boiler) is specified over the z_in input. The vapor fraction (vf =
VaporFraction) as well as the composition in the liquid (x_out) and in the gas phase (y_out) is
calculated and then made available at the output.
The evaporator can be used as evaporator of a column with natural circulation. To do so, the
ThermoSyph connector must be connected to the corresponding connector of the column. The
necessary information (heat flow, vapor fraction, compositions, kVS value of the cold side at the
interpolation point) is exchanged with the column for the natural circulation via this connector.
For the natural circulation, the current kVS value on the cold side of the evaporator is adjusted
so that the mass flow of the natural circulation is set depending on the differences in density.
The evaporator is parameterized via the heat exchange surface and the heat transfer
coefficient. The mixture to be vaporized is defined over the boiling temperature of the low and
high boiler (TS_LB, TS_HB) as well as over their vaporization enthalpies (hv_LB, hv_HB). The
size of the boiling lens can be varied using the S parameter. This means:
● S = 0, maximum size of the boiling lens (see figure).
● S = THB − TLB, no boiling lens (makes no sense physically)
7HPSHUDWXUH>r&@
7HPSHUDWXUH>r&@
0DVVIUDFWLRQKLJKERLOHU 0DVVIUDFWLRQKLJKERLOHU 0DVVIUDFWLRQKLJKERLOHU
>NJNJ@ >NJNJ@ >NJNJ@
Tau line
Boiling point curve
Figure 8-20 Boiling lens as a function of the parameter S (spread)
NOTICE
The flow direction is permanently set on the cold side. A flow is always only possible from the
input (CIn) to the output (COut). A flow due to a difference in pressure from the output to the
input is prevented by a modeled check valve.
The flow direction is permanently set on the warm side. A flow is always only possible from the
input (HIn) to the output (HOut). A flow due to a difference in pressure from the output to the
input is prevented by a modeled check valve.
A flownet with the medium Liquid must be connected at the input on the cold side (CIn). A
flownet with the medium Ideal gas must be connected at the output on the cold side (COut).
Parameter
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The ElectricHeatExchanger component type is used for simulation of an electrical heater in the
flow network. The electrical heating power Pel in kW is specified with the connector P_EL.
It is assumed that the supplied electrical energy Pel is completely converted into heat. There are
no losses.
GK &
4
GW ˮ9
The ElectricHeatExchanger component is inserted in a flow network using the connectors A
and B. Flows can enter this component type from both ends.
The size of the heat exchanger can be configured with the Volume parameter. The result is a
delayed temperature change at the output side of the medium when the heating power is
switched on or off.
The volume is always considered to be fully filled, which means that mass is neither added nor
removed.
The pressure drop across the component is set with the Kvs parameter.
To prevent undesirable states of the simulation, the maximum enthalpy of the outflowing
medium can be specified with the MaxEnthalpy parameter.
Note
You can also use this component for cooling by specifying a negative heating power Pel at
the P_EL input.
NOTICE
The ElectricHeatExchanger calculates only heat transfers and not related density changes. If
the ElectricHeatExchanger is being operated in a water-steam flow network, these density
changes are only calculated in the next flowed-through node.
For this reason, a measuring point in the same branch positioned directly after
the ElectricHeatExchanger still operates with the unchanged density. The temperature T = f(p,
h) calculated within this measuring point is thus not exact.
For an exact calculation, a node is needed between ElectricHeatExchanger and the
measuring point.
Parameters
See also
Geodetic height (Page 588)
HeatExchangerGeneral
Symbol
Function
The HeatExchangerGeneral component is a model of a general heat exchanger. Heat is
exchanged between the product side (PS) and the service side (SS). The heat exchanger is
configured on the basis of the heat exchanger area, the heat transfer coefficient and the
minimum temperature difference between the product and service side. Heat transferred is
calculated using the logarithmic mean temperature difference. If the temperature difference is
below the minimum, the flow is adjusted to comply with the minimum temperature difference.
The two mediums are connected at connections P1 and P2 on the process side and
connections S1 and S2 at the service side. The heat exchanger operates as either a
countercurrent or parallel-flow exchanger (see table).
NOTICE
The model is not suitable for calculating the phase change at the product or service side when
the medium water/steam is connected. Deviations can occur in the calculation of the heat flow
and therefore in outlet temperatures. There are therefore three ranges for component
calculation:
● Supercooled liquid – boiling liquid:
● Boiling liquid – saturated steam
● Saturated steam – superheated steam
Display
During simulation, the direct of flow is displayed in color in the symbol of the component. This
direction is indicated by the heat flow sign in the heat exchanger calculation.
If the calculated heat flow is limited by a phase change, the lines will be gray:
If an error occurs in the calculation of the heat flow, the lines will turn red:
This is not a problem if the symbol only appears briefly, for example during a load change.
However, if the problem persists over a longer period of time, check the set parameters or the
corresponding load points.
Parameter
Additional parameters
Evaporation/condensation frequently accounts for a large proportion of the heat flow. When
you select water/steam as the medium, you can force calculation of condensation/evaporation
with the options PhaseChangePS (for the process side) and PhaseChangeSS (for the service
side). This runs a calculation in the wet steam area (area 2). Any heat from superheated steam
and supercooled liquid is disregarded.
For the calculation to be run, the input temperatures at the heat exchanger must meet the
physical requirements. If the option is not selected, the calculation only runs until the wet steam
i.e. saturated steam or saturated liquid range is reached. There is no phase change.
Operating window
The following variables are displayed in the operating window:
See also
Geodetic height (Page 588)
Symbol
Function
The HeatExchangerShellTube component is the model of a single-pass counter-flow shell and
tube heat exchanger. The component is therefore configured using corresponding geometric
data.
Both media are routed on the tube side via the connectors TS_IN and TS_OUT, and on the shell
side via the connectors SS_IN and SS_OUT.
If the flow direction is reversed on one side, the heat exchanger works accordingly as a parallel-
flow heat exchanger.
A total volume for the tube inside and for the shell side is calculated based on the configured
geometric data. The transfer area is the sum of the transfer areas of the individual tubes.
The figure below therefore shows the resulting single-tube model.
① Tube-side space
② Tube
③ Shell-side space
Figure 8-24 Structure of the single-tube model in component type HeatExchangerShellTube
This model is segmented to simplify the calculation. The number of segments is specified with
the NbrOfSegments parameter. Perfect mixing of the respective medium is assumed within a
segment. This approach produces a quantization error.
The number of segments can be selected between 2 and 20.
The heat transfers between the tube interior, tube material and shell space can be set using the
HTC_TS (tube space → tube) and HTC_SS (tube → shell space).
Heat losses to the surrounding area over the shell can be configured with the HTC_Shell
parameter. The heat loss is calculated depending on the ambient temperature
(AmbientTemperature input).
The "stable condition" state in the operating window can no longer be achieved in this case
because the heat flow Q (SS-Tube) also includes the heat losses over the shell.
Note
Select the optimal number of segments.
A larger number of segments reduces the risk of a discretization error.
However, too many segments can increase the computational load and cause instabilities.
In the unstable state, the heat exchanger displays the following symbol:
This is not a problem if the symbol only appears briefly, e.g. during a load change. However, if
the problem persists over a longer period of time, check the set parameters or the
corresponding load points. You increase stability, for example, by reducing the number of
segments or the mass flow.
The type of medium on the shell or tube side results from the connection of the heat exchanger
in the flow network and does not have to be configured separately.
The heat capacity of the metal (tubes and shell) is permanently set at 0.46 kJ/(kg⋅K).
NOTICE
The HeatExchangerShellTube calculates only heat transfers and not related density changes.
If the HeatExchangerShellTube is being operated in a water-steam flow network, these
density changes are only calculated in the next flowed-through node.
For this reason, a measuring point in the same branch positioned directly after
the HeatExchangerShellTube still operates with the unchanged density. The
temperature T = f(p, h) calculated within this measuring point is thus not exact.
For an exact calculation, a node is needed between HeatExchangerShellTube and the
measuring point.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
A filled box ("stable condition") indicates that a constant throughflow with stable heat transfer
has been reached.
See also
Geodetic height (Page 588)
Symbol
Function
The HeatPipe component type is used for simulation of an electrically heated pipe. The
electrical heating power Pel in kW is specified with the connector P_EL.
It is assumed that the supplied electrical energy P_EL is completely converted into heat. There
are no losses.
GK &
4
GW ˮ9
The HeatPipe component is inserted in a flow network using the connectors A and B. Flows can
enter this component type from both ends.
You can configure the size of the heated pipe using the Volume parameter. The result is a
delayed temperature change at the output side of the medium when the heating power is
switched on or off. However, the pipe volume is considered to be perfectly mixed, so that the
temperature throughout the entire pipe volume is uniform and is slowly increased or decreased
according to the temperature change.
The volume is always considered to be fully filled, which means that mass is neither added nor
removed.
The pressure drop across the component is set with the Kvs parameter.
To prevent undesirable simulation states, you can specify the maximum possible enthalpy of
the outflowing medium using the MaxEnthalpy parameter.
Note
You can also use this component for cooling by specifying a negative heating power Pel at
the P_EL input.
When heating mode is active, this is indicated by a red heating coil in the symbol of the
HeatPipe component.
NOTICE
The HeatPipe component calculates only heat transfers and not related density changes. If
the HeatPipe is being operated in a water-steam flow network, these density changes are only
calculated in the next flowed-through node.
For this reason, a measuring point in the same branch positioned directly after the HeatPipe
still operates with the unchanged density. The temperature T = f(p, h) calculated within this
measuring point is thus not exact.
For an exact calculation, a node is needed between HeatPipe and the measuring point.
Parameters
Additional parameters
8.2.5.5 Measurements
Symbol
Function
The DifferencePressureIndicator component type displays the difference of the pressures
specified using its inputs Measure1 and Measure2.
You can specify a high or low limit for the measured value with the SwitchValue_Plus or
SwitchValue_Minus parameter. You can enable limit monitoring with the Use_Plus and
Use_Minus switches. A green binary indicator in the symbol shows that the high or low limit has
been reached.
You can set the unit for the analog output and the switching limits with the UoM parameter.
If multiple switch values are required, then you must also use multiple measuring points.
Alternatively, you can configure additional binary values using logic functions.
For additional linking of measured values, you can make the following outputs of the
component visible:
● AOUT
Connection of the analog value with the unit set with parameter UoM
● BOUT_PLUS
Connection of the binary value of the high limit
● BOUT_MINUS
Connection of the binary value of the low limit
The state of these switch values is displayed dynamically in the graphic symbol:
Parameters
Operating window
The following variable is displayed in the operating window:
DriveIndicator
Symbol
Function
The DriveIndicator component type only has graphic functions. It is used to illustrate the signal
path for the control of drives.
If necessary, you can also use this component directly for controlling drives. To do so, you
connect the component to the actuator-sensor level using the DI input. The DO output is then
connected, for example, to the controlling input of the valve or a pump.
Parameter
Symbol
Function
The FlowIndicator component type displays the flow specified using its Measure input.
You can specify a high or low limit for the measured value with the SwitchValue_Plus or
SwitchValue_Minus parameter. You can enable limit monitoring with the Use_Plus and
Use_Minus switches. A green binary indicator in the symbol shows that the corresponding
switch value has been reached.
You can set the unit for the analog output and the switching limits with the UoM parameter.
For additional linking of measured values, you can make the following outputs of the
component visible:
● AOUT
Connection of the analog value with the unit set with parameter UoM
● BOUT_Plus
Connection of the binary value of the high limit
● BOUT_Minus
Connection of the binary value of the low limit
The state of these switch values is displayed dynamically in the graphic symbol:
Parameters
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The LevelIndicator component type displays the level specified using its Measure input.
You can specify a high or low limit for the measured value with the SwitchValue_Plus or
SwitchValue_Minus parameter. You can enable limit monitoring with the Use_Plus and
Use_Minus switches. A green binary indicator in the symbol shows that the high or low switch
value has been reached.
You can set the unit for the analog output and the switching limits with the UoM parameter.
For additional linking of measured values, you can make the following outputs of the
component visible:
● AOUT
Connection of the analog value
● BOUT_Plus
Connection of the binary value of the high limit
● BOUTMinus
Connection of the binary value of the low limit
The state of these switch values is displayed dynamically in the graphic symbol:
Parameters
Operating window
The following variable is displayed in the operating window:
NozzleMeasurement
Symbol
Function
The NozzleMeasurement component is used for connecting measuring points
(e.g. LevelIndicator or TemperatureIndicator) to another component (e.g. StorageTankLiquid
or PressureStrainer).
The component transmits the values pending at input A to the output B. The values remain
unchanged
Symbol
① Measure
Figure 8-35 Symbol of component type PipeMeasure
Function
The PipeMeasure component type forms a measuring point in the tube. You insert it with its
connectors A and B at the desired measuring point in the flow network.
The following measured variables are output via connector Measure:
● Absolute value |ṁ| of the flow
● Pressure pA at connector A
● Temperature T
All other signals of connector Measure are not set in this component.
Note
The measuring procedures for the different variables are not simulated with suitable models.
Only the quantities calculated in the flow network solver are output.
The direction of the media flow is indicated by an arrow in the symbol during active simulation
(see figure).
P
& ! P
&
Parameter
Operating window
The following variables are displayed in the operating window:
Temperature T °C
See also
Geodetic height (Page 588)
Symbol
Function
The PressureIndicator component type displays the pressure value specified using its Measure
input.
You can specify a high or low limit for the measured value with the SwitchValue_Plus or
SwitchValue_Minus parameter. You can enable limit monitoring with the Use_Plus and
Use_Minus switches. A green binary indicator in the symbol shows that the high or low switch
value has been reached.
You can set the unit for the analog output and the switching limits with the UoM parameter.
For additional linking of measured values, you can make the following outputs of the
component visible:
● AOUT
Connection of the analog value with the unit set with parameter UoM
● BOUT_Plus
Connection of the binary value of the high limit
● BOUT_Minus
Connection of the binary value of the low limit
The state of these switch values is displayed dynamically in the graphic symbol:
Parameters
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The TemperatureIndicator component type displays the temperature specified using
its Measure input.
You can specify a high or low limit for the measured value with the SwitchValue_Plus or
SwitchValue_Minus parameter. You can enable limit monitoring with the Use_Plus and
Use_Minus switches. A green binary indicator in the symbol shows that the high or low switch
value has been reached.
You can set the unit for the analog output and the switching limits with the UoM parameter.
For additional linking of measured values, you can make the following outputs of the
component visible:
● AOUT
Connection of the analog value with the unit set with parameter UoM
● BOUT_Plus
Connection of the binary value of the high limit
● BOUT_Minus
Connection of the binary value of the low limit
The state of these switch values is displayed dynamically in the graphic symbol:
Parameters
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The WeightIndicator component type displays the weight specified using its Measure input.
You can specify a high or low limit for the measured value with the SwitchValue_Plus or
SwitchValue_Minus parameter. You can enable limit monitoring with the Use_Plus and
Use_Minus switches. A green binary indicator in the symbol shows that the high or low switch
value has been reached.
You can set the unit for the analog output and the switching limits with the UoM parameter.
For additional linking of measured values, you can make the following outputs of the
component visible:
● AOUT
Connection of the analog value with the unit set with parameter UoM
● BOUT_Plus
Connection of the binary value of the high limit
● BOUT_Minus
Connection of the binary value of the low limit
The state of these switch values is displayed dynamically in the graphic symbol:
Parameters
Operating window
The following variable is displayed in the operating window:
Mixer
Symbol
Function
The mixer is used to add a partial mass flow C (e.g. of a solid matter mass fraction or of a liquid
mass fraction) to a main flow AB.
The mass fraction of the fed partial mass flow in the main flow is calculated in the mixer. This
can be useful, for example, in a circulating circuit when a second substance is added (e.g.
concentration of an acid).
The flow network of the fed-in partial mass flow C is not connected topologically to the flow
network of the main mass flow AB. The change of the material properties (e.g. heat capacity)
of the exiting main flow due to addition of partial flow C is disregarded.
If solid matter is added, it is handled like a liquid. A pressure difference is therefore necessary
for a solid matter transport The reason being is that the flow network in SIMIT generally only
permits the transport of gases and liquids. Any conveying equipment is replaced with
equivalent connections (consisting of pumps, valves, sources and sinks).
The main mass flow can flow in both directions. The fed partial mass flow always flows into the
mixer. For this to work, a higher pressure is required in the flow network of the partial mass flow
than in the main mass flow.
6XSSOLHGSDUWLDOPDVV 6XSSOLHGSDUWLDOPDVV
IORZ IORZ
0DLQIORZ 0DLQIORZ
The main flow connectors A and B are designed identically. The partial mass flow to be added
is always fed through the connector C.
You can use the Mixer component to specify a mass fraction for the partial masses for each
individual substance flow connector at the inputs RateA, RateB or RateC.
If none of the three connectors is specified (default setting), the following applies:
● 0 % mass fraction in the main flow entry
● 0 % mass fraction in the partial mass flow entry
The mass fraction of the total flow exiting at A or B is calculated and displayed at the output
Rate.
A pressure drop is calculated for the main mass flow. This pressure drop depends on:
● Flow coefficient of the mixer (kVS value)
● Throughflow (volume flow, medium)
The pressure drop above the mixer is calculated using the formula below:
ෙS P& VHF
EDU NJ K
N96 ˮ
Whereby:
NOTICE
The flow network of the feed-in mass flow at connector C is terminated in the component with
a mass flow source.
Because of this mass flow source, the pressure reached at the edge of the flow network is
dependent on the fed mass flow and the pressure drop in the feeding branch. Pressure drops
that are too high in the feeding branch (for example too low kVS values in the main flow) can
result in impossible physical states.
Parameters
Operating window
The following variables for the following mass flows are displayed in the operating window:
● Incoming main mass flow A or B
● Added mass flow C
● Outgoing total mass flow A or B
See also
Geodetic height (Page 588)
8.2.5.7 Pump
Compressor
Symbol
Function
The Compressor component type calculates the pressure increase in gas flowing through a
compressor as a function of the flow rate and speed using the following formula:
ෙ3 Q ෙ3 ෙ3
ෙ3 9&
IRU 9& !
9&
ΔP Current pressure increase in the compressor [bar]
ΔP* Rated pressure increase in the compressor at the design point [bar]
ΔP0 Zero flow head of the compressor [bar]
n Normalized current speed [0..1]
v̇ Current flow rate in the compressor [Nm³/s]
v̇* Rated flow rate in the compressor at the design point [Nm³/s]
For the flow rate v̇, the reference direction is defined from connector A to connector B; i.e. for
a flow rate in the reference direction, v̇ > 0.
The speed is specified as a percentage value at the Speed input. The speed value is limited to
the range 0 ≤ N ≤ 100 %. This means n = n = N / 100 % and thus 0 ≤ n ≤ 1. This speed value
can be linked, for example, over an I/O level as described in Coupling simulation model with
actuator/sensor level (Page 601) to a control technology using the drives from the SIMIT basic
library.
The following figure illustrates the above quadratic relationship between pressure increase and
flow rate during compressor operation in the standard range, which means for v̇ > 0, ΔP > 0.
ෙ3
ෙ3
Q
3
Q ෙ
① Compressor limit
.
3% .
7% 7$
3$
There is no pressure increase following a flow reversal (v̇ < 0). The compressor behaves like
a check valve in this case. You set the throttle effect in this case using parameter Kv0.
Note
The Compressor component only compresses gases. For liquids and water, the pump only acts
as a flow resistor with the resistance coefficient Kv0. Water/steam is compressed with a liquid
proportion of up to 5 Ma.%.
Parameters
ෙ3
ෙ3
ෙ3
9& 9&
Additional parameters
Operating window
You switch between automated control (control using the actuator-sensor level) and manual
control in the operating window. The default is always automated control. The following
variables are displayed in the operating window:
The compressor characteristic curve is displayed graphically in the extended operating window
of the Compressor component type. The following variables are also displayed:
See also
Geodetic height (Page 588)
Pump
Symbol
① Speed
Figure 8-45 Symbol of component type Pump
Function
The Pump component type calculates the pressure increase through a pump as a function of
flow rate and speed according to the following formula:
Q ෙS ෙS
ෙS
P
&
ෙS IRU P
& !
P&
Δp Current pressure increase of the pump [bar]
Δp* Rated pressure increase of the pump at the design point [bar]
Δp0 Zero flow head of the pump [bar]
n Normalized current speed [0..1]
ṁ Current flow rate of the pump [kg/s]
ṁ* Rated flow rate of the pump at the design point [bar]
For the flow rate ṁ, the reference direction is defined from connector A to connector B; for a flow
rate in reference direction, ṁ > 0.
The speed is defined as percentage at the Speed input. The speed value is limited to the range
0 ≤ N ≤ 100 %. This means n = n = N / 100 % and thus 0 ≤ n ≤ 1. This speed value can, for
example, be connected over its I/O level as described in Coupling simulation model with
actuator/sensor level (Page 601) to a control technology using the drives from the SIMIT basic
library.
The following figure illustrates the above-defined quadratic relationship between pressure
increase and flow rate during pump operation in the standard range, which means for ṁ > 0,
Δp > 0, in the figure below.
3UHVVXUHLQFUHDVH
ෙ3
ෙ3
&
ෙ3
P
Q
Q ෙ3
)ORZUDWH
P&
QP
& P
&
There is no pressure increase following a flow reversal (ṁ < 0). The pump behaves like a check
valve in this case. You set the throttle effect in this case using parameter Kv0.
Parameters
The determining variables of the pump characteristic are set with parameters:
ෙ3
ෙ3
ෙ3
&
P P
&
Additional parameters
The operating state in the pump symbol is displayed as follows (see figure):
P
& P
& ! Q ෙ3
Figure 8-48 Display of the operating state of the pump at the symbol
Operating window
You switch between automated control (control using the actuator-sensor level) and manual
control in the operating window. The default is always automated control.
For manual control, you specify the pump speed as a percentage using a slider.
The pump characteristic is displayed graphically in the extended operating window. The
characteristic values of the characteristic curve and the current operating point are indicated via
digital displays. In addition, the current pressure increase Δp and the flow rate ṁ are displayed.
See also
Geodetic height (Page 588)
8.2.5.8 Separators
Centrifuge
Symbol
Function
The component type Centrifuge is used to separate a mixture (suspension or emulsion)
consisting of two substances into its individual components. This component cannot be used
to separate gas mixtures.
Separation in a centrifuge is the result of inertia during operation of the centrifuge (rotation of
the centrifuge chamber). Particles with greater density are propelled to the outside or solid
matter is retained due to installed parts (e.g. screen or filter cloth).
In this model, the separation is simulated by defining a separable mixture component and a non-
separable mixture component. The sum of both fractions is 100%. Different densities are
ignored during the separation.
The part that is propelled to the outside is referred to as filtrate below (separable mixture
component). The part that remains in the centrifuge chamber is referred to as filter cake below
(non-separable mixture component).
The filter cake can be dissolved again and washed out by adding water. By adding pressurized
gas, the liquid can be forced out of the filter cake.
Circuit
The centrifuge has two types of connectors for material flows and thus for connection of
pipelines:
● N1 ... Nn – general connecting pipes
These connection points are used to fill and empty the centrifuge and as gas connections.
All connectors of the vector N1..Nn are initially equal and can be used for all connection
types (water/steam, ideal gas, liquid).
● F1 … Fn – Filtrate drain
These connection points are a special case. The filtrate exits the system through these
connections. All other connections are made using the vector N1..Nn described above.
The number of connection points depends on the system to be simulated and is specified with
the parameters NbrOfInletsOutlets for the connectors N1 ... Nn and NbrOfFiltrateOutlets for the
connectors F1 ... Fn.
The material medium in the neighboring flow networks is defined over the NetParam
component.
The minimum connection is:
● Emulsion/suspension inflow (Nn)
● Filter cake discharge (mixture fraction with low density or held back in the centrifuge
chamber) (Nn)
● Filtrate discharge (mixture fraction expelled from the centrifuge chamber) (Fn)
Possible additional connections include:
● Inflow/discharge of cleansing agents
● Inflow/discharge of washing solutions
● Gas inflow and gas emission
● Ventilation
For the water/steam connector type, the incoming medium is mixed internally in the tank with
a liquid medium. The inflowing mass and enthalpy is taken into account but a corresponding
phase equilibrium does not form in the model. Incoming steam is added to the liquid phase in
the mass balance and does not contribute to building the pressure in the gas phase. Water is
handled in the mixture like a liquid medium.
If water/steam is used as a discharge medium, it exits the centrifuge at the output with the
mixture enthalpy of the liquid phase. All other calculations within this flow network are made
using the properties of water/steam (e.g. heat capacity).
Due to the lack of steam properties, steam sterilization, for example, is currently not possible
even at standstill.
Parameter ConnectorHeight
For each of the connection points N1..Nn and F1..Fn you need the installation height of the
connecting pipe on the centrifuge (parameter ConnectorHeight for connectors N1..Nn
or ConnectorHeightF for connectors F1..Fn). The information is entered in meters. The default
is 0 m and thus at the bottom of the centrifuge. Negative values are permitted for simulation of
connectors at a lower position.
Q
GP/LTXLG
GW P& /LTXLGL
L
Q
GP6FUHHQLQJ
GW P& 6FUHHQLQJL
L
GK/LTXLG Q
P
& /LTXLGL K/LTXLGL 4&
GW P/LTXLG L
K/LTXLG
7/LTXLG
F3
Q
GP*DV
GW P& *DVL
L
GK*DV Q
P
& *DVL K*DVL 4&
GW P*DV L
The gas pressure is then calculated according to the state equation of ideal gases:
P*DV 56 7*DV
S*DV
9*DV
If a gas connector is not connected, the gas balance calculation does not take place. In this
case, the gas pressure is replaced with the atmospheric pressure.
The component type Centrifuge has different symbols for operation with and without gas
pressure.
A distinction is not made between suspension and emulsion within the component type. In case
of a suspension, the internal calculation still takes place with two liquids. The corresponding
removal of the filter cake of a suspension is thus also as a "liquid medium". Devices used for
output (scrapers, screw conveyors, or similar) must therefore be replaced with valves and
pumps in the model.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Connection example
The figure below shows an example of the connection of a centrifuge:
Figure 8-51 Parameter assignment of component type Centrifuge in the connection example
See also
Geodetic height (Page 588)
Column
Symbol
Function
The Column component type calculates the distillation of a binary feed flow to a low boiling
mixture (overhead product) and a high boiling mixture (bottom product) in a plate column.
The feed flow enters the column through the F connection with the concentration of low-boiler
x_F. The top product (distillate) is taken from the column at connection D with the concentration
of high-boilers x_D. The bottom product (bottom) is taken from the column at connection B with
the concentration of high-boilers x_B.
There is a condenser with a reflux vessel at the top of the column. The condenser has two
connections for cooling water (CW_in and CW_out). A pump (either in the reflux vessel drain or
in the reflux line) pumps the reflux into the column. Constituents of the column top stream that
have not condensed are removed from the column through connection I.
In the sump, the column is heated by a natural convection evaporator (reboiler). The reboiler
has two connections for heating steam (ST_in and ST_out).
The separation of the low-boiling and high-boiling fractions is calculated in idealized terms
using split factors. The split factors are determined using empirical formulas depending on
reflux flow, boilup flow, feed flow and feed concentration compared to the (stationary) operation
point (OP). The stationary operation point is specified with the following parameters:
● Feed flow: OP_mflF
● Feed concentration: OP_xF
● Top concentration: OP_xD
● Bottom concentration: OP_xB
● Reflux amount: OP_mflR
● Boilup amount: OP_mflV
● Evaporator output: OP_Qreb
The split factors are limited with the Split_Max parameter. The maximum split factor is
Split_Max and the minimum is (1 – Split_Max). The greater the individual split factor, the more
the high-boilers or low-boilers are separated through the top stream.
The temperatures in the column are calculated at column operating pressure as a function of
the concentration of low-boiling fraction x and the boiling points of the low-boiling and high-
boiling fraction (TS_LB and TS_HB).
The Pump_Top parameter allows you to choose whether the pump is at the reflux vessel or in
the reflux line (Reflux) or whether the pump is in the drain of the reflux vessel for reflux and
distillate (Reflux+Distillate).
Parameters
Additional parameters
Operating window
The key column characteristics are displayed in the operating window. The following variables
are displayed:
Column Tower
Symbol
Function
The Column Tower component type calculates the distillation of a binary feed flow to a low
boiling mixture (overhead product) and a high boiling mixture (bottom product) in a plate
column.
The feed flow is supplied to the column over the F connector with the concentration of low
boilers zF. The overhead product (distillate) is taken from the column at the D connector with
the concentration of low boilers xD. The bottom product (bottom) is taken from the column at the
B connector with the concentration of low boilers xB. The return flow is supplied at the R
connector with the concentration zR. The bottom flow to the reboiler is removed at the L
connector. The heated and partially evaporated flow from the reboiler is once again returned to
the column at the V connector. The concentration of low boilers for this flow is input via the zV
connector.
The separation of low boilers and high boilers is calculated idealized using so-called split
factors. The split factors are determined using empirical formulas depending on reflux flow,
boilup flow, feed flow and feed concentration compared to the (stationary) operation point (OP).
The stationary operation point is specified with the following parameters:
● Feed flow OP_mflF
● Feed concentration OP_xF
● Overhead concentration OP_xD
● Bottom concentration OP_xB
● Reflux flow OP_mflR
● kVS value evaporator OP_kvReb (for natural circulation) or
● Circulation flow OP_mflCircForced (for forced circulation)
The split factors are limited with the Split_Max parameter. The maximum split factor is
Split_Max, the minimum split factor is (1 – Split_Max). The greater the individual split factor, the
more low boilers or high boilers are separated over the overhead product flow.
The temperatures in the column are calculated based on the concentration of the low boiler x
and the boiling points of the low boiler and high boiler (TS_LB and TS_HB) as well as the spread
S of the boiling lens at column operation pressure.
T = f (TSLB,TSHB,S,x)
The ThermoSiph connector of the column can be connected to the ThermoSiph connector of
the evaporator/reboiler. The necessary information such as steam mass content vf and
composition of the steam and liquid phase (x and y) at the reboiler output as well as the bottom
concentration of the xB column is then transferred directly. If this connector is connected, you
no longer need to specify the input zV.
The ThermoSiphon parameter can be used to set that the reboiler is operated as natural
circulation evaporator. In this case the ThermoSiph connector of the column can be connected
to the ThermoSiph connector of the evaporator. The natural circulation between column and
evaporator is then implemented accordingly. If the ThermoSiphon parameter is not set, we
assume a forced circulation with pump. The ThermoSiph connector can also be connected to
the evaporator here.
The column size is specified with the following parameters:
● Column diameter Diameter
● Number of trays n_tray
● Tray height Tray_Height
The feed tray of the column is specified with the Feed_Tray parameter.
The reflux vessel is configured with the diameter Diameter_RefluxVessel and volume
Volume_RefluxVessel parameters. If the reflux vessel runs empty, the vessel is shown with
blue lines. If the vessel is completely filled and overflows, the vessel is shown with red lines (see
figure).
The level, pressure and temperature in the column sump can be read off at process tag I/O
Bottom.
Measurements (pressure and temperature) at the column can be read out over the measuring
point connectors Measurement[i]. The number can be specified with the NbrOfMeasurements
parameter. The tray on which the measuring point is located can be specified for each
measuring point with the MeasurementsTray parameter.
Parameter
The following parameters are available:
Additional parameters
The following additional parameters are available:
Operating window
The key column characteristics are displayed in the operating window. The following variables
are displayed:
Filter
Symbol
Function
The Filter component simulates the behavior of a filter in a pipeline in the form of a pressure
drop.
This pressure drop depends on:
● Flow coefficient of the clean filter (kVS value)
● Throughflow (volume flow, medium)
● Clogging of the filter (Clogging)
The pressure drop across the filter is calculated according to the following formula:
ෙS P& VHF
EDU NJ K
N96
FORJJLQJ ˮ
P
Whereby:
For the media flow ṁ, the reference direction is defined from connector A to connector B, which
means for a media flow in reference direction ṁ > 0. This means the pressure drop therefore
has a negative value: Δp < 0.
This fact is also represented by an arrow in the symbol.
You can configure a clogging rate using the CloggingRate parameter. This parameter indicates
the clogging rate in percentage per mass passing through. You can use this to model a filter
whose clogging rate and therefore pressure drop increase at a certain rate.
To simplify matters, we assume that the incoming mass flow is equal to the outgoing mass flow
at any time. The partial mass flow filtered out from the main flow is thus neither removed from
the main mass flow nor added or taken away.
You can clean the filter using the "Clogging Reset" button. This function can also be connected
externally using the Reset input (e.g. after expiration of a sequence for purging the filter).
Parameters
Operating window
The following variables are displayed in the operating window:
Clogging1 – %
1
Can be reset with "Reset"
PressureStrainer
Symbol
Function
The PressureStrainer component type simulates the functionality of a pressure strainer.
The pressure strainer is a filter in which a suspension is mechanically separated. To do this, the
pressure strainer is filled with a suspension. The pressure strainer is then subjected to an
overpressure, which presses the filtrate through a filter floor, thereby achieving the separation.
Additional steps can be executed between filling the strainer and applying the pressure, such
as
● Sedimentation of the solid matter on the floor
● Smoothing of the layer on the floor caused by sedimentation using an agitator
The pressure strainer component is modeled as perfectly mixed. The above-named steps can
thus not be simulated. However, corresponding actions can be simulated in the actuator/sensor
level, such as:
● Wait times of the agitator
● Activities of the agitator (CCW / CW rotation, speeds, agitation time, etc.)
The effects of these actions are generally not directly measurable in the pressure strainer.
If you need individual effects from these actions, you must model them additionally using logic
blocks.
By applying pressure to the strainer, the filtrate is slowly pressed through the filter floor. As soon
as a configurable level of dryness DryingRate is reached in the filter cake, a "breakthrough" of
the gas occurs. The gas thereby escapes from the strainer space through drying cracks in the
filter cake. The pressure drop associated with this process represents the end of filtration for the
component. Additional drying is now only possible by heating the pressure strainer.
The filter cake is output as liquid medium. Devices used for output (scrapers, screw conveyors,
or similar) must therefore be replaced with valves and pumps in the model.
The component type PressureStrainer offers the option of connecting a heating or cooling
jacket for drying (HeatingJacket, ElectricalHeatingJacket component). A heat input, e.g. by
means of an agitator, is possible using input Q.
Within the component type PressureStrainer, the separation occurs in a simplified manner by
removal of the various fractions (filtrate and filter cake) from partial mass balances. The
structure of the filter cake and the actual filter floor are not modeled.
Circuit
The PressureStrainer component has two types of connectors for material flows and thus for
connection of pipelines:
● N1 ... Nn – general connecting pipes
These connection points are used to fill and empty the pressure strainer and as gas
connections.
All connectors of the vector N1..Nn are initially equal and can be used for all connection
types (water/steam, ideal gas, liquid).
● F1 … Fn – Filtrate drain
These connection points are a special case. The filtrate exits the system through these
connections. All other connections are made using the vector N1..Nn described above.
The number of connection points depends on the system to be simulated and is specified using
the parameters NbrOfConnectors for N1 ... Nn and NbrOfFiltrateConnectors for F1 ... Fn.
The material medium in the neighboring flow networks is defined over the NetParam
component.
The minimum connection is:
● Suspension entry (Nn)
● Filter cake discharge (fraction of mixture with low density) (Nn)
● Filtrate discharge (fraction of mixture with higher density) (Fn)
● Gas connector (Nn)
Possible additional connections include:
● Inflow/discharge of cleansing agents (Nn)
● Inflow/discharge of washing solutions (Nn)
● Additional gas inflow and gas emission (Nn)
For the water/steam connection type, the inflowing medium is mixed with a liquid medium inside
the pressure strainer. The inflowing mass and enthalpy is taken into account but a
corresponding phase equilibrium does not form in the model. Incoming steam is added to the
liquid phase in the mass balance and does not contribute to building the pressure in the gas
phase. Water is handled in the mixture like a liquid medium.
If water/steam is used as a discharge medium, the mixture enthalpy of the liquid phase is
specified at the corresponding material output of the centrifuge. All other calculations within this
flow network are made using the properties of water/steam (e.g. heat capacity).
Due to the lack of steam properties, steam sterilization, for example, is therefore currently not
possible even at standstill.
Parameter ConnectorHeight
For each of the connection points N1..Nn and F1..Fn you need the installation height of the
connecting piece on the pressure strainer (parameter ConnectorHeight for connectors N1..Nn
or ConnectorHeightF for connectors F1..Fn). The information is entered in meters. The default
is 0 m and thus at the bottom of the pressure strainer. Negative values are permitted for
simulation of connectors at a lower position.
Examples:
● Product suspension – e.g. 90%
● Solvent: 0%
● Rinsing liquid: 0%
The values defined here only apply to incoming substance flows. All outgoing material flows exit
with the solid matter concentration currently stored in the centrifuge. This value is available to
the user at the Rate output for additional calculations. Any entered SolidFraction is not
evaluated in this case.
The filtrate discharges F1..Fn are an exception once again. These outflows are always pure
filtrate. This means there are no connectors SolidFraction for the filtrate discharges F1..Fn. If
these connectors are used as inputs, balancing takes place with the SolidFraction = 0.0
(without separable components).
The input vector SolidFraction is not visible by default.
Alternatively, you can also manually set the SolidFraction parameter of the filled pressure
strainer after the filling operation via the operating window.
Q
GP/LTXLG
GW P& /LTXLGL
L
Q
GP6FUHHQLQJ
GW P& 6FUHHQLQJL
L
GK/LTXLG Q
P
& /LTXLGL K/LTXLGL 4&
GW P/LTXLG L
K/LTXLG
7/LTXLG
F3
As soon as the solid matter concentration currently stored in the tank Rate corresponds to the
configured dryness level DryingRate, a pressure breakthrough of the filter cake occurs. The
gas pressure in the pressure strainer drops abruptly. This pressure drop is indicated in the
symbol by a color change of the cross-hatched filter zone to red.
Figure 8-55 Symbol of the PressureStrainer upon reaching the configured dryness level DryingRate
(pressure breakthrough)
The gas balance calculation only refers to externally added (inert) gases, however. Steam
pressures of solvents are not taken into account.
The incoming and outgoing masses and enthalpies are balanced within the gas-filled space:
Q
GP*DV
GW P& *DVL
L
GK*DV Q
P
& *DVL K*DVL 4&
GW P*DV L
The gas pressure is then calculated according to the state equation of ideal gases:
P*DV 56 7*DV
S*DV
9*DV
The gas temperature TGas is calculated from the balanced gas enthalpy hGas. If the gas
temperature and liquid temperature are different, a corresponding temperature equalization
occurs during simulation.
The absolute value of the filtrate mass flow can be set by means of kV values in the filtrate drain
(e.g. valve or nozzle). An additional component is required to do this.
For this, you must first enter the setpoint in the corresponding digital input SetValues and apply
it with the "Set" button. You can specify the state of the stored mass using the "Mass" value as
well as using the fill level (Level).
By manipulating state variables in this way, you can, for example, speed up heating processes
or filling processes. As the operator, you can also empty the pressure strainer, for example, to
return to an earlier step in a step sequence.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Connection example
The figure below shows an example for connection of a pressure strainer while using
components of the CHEM-BASIC library.
The following parameter assignment of the PressureStrainer component is used for this
connection example:
Figure 8-57 Parameter assignment of component PressureStrainer for the connection example
See also
Geodetic height (Page 588)
Screening device
Symbol
Function
The component type ScreeningDevice is used to separate a partial mass flow from a total mass
flow.
Example:
● Separation of a specific particle size from a total batch
● Separation of a solids fraction from a suspension
This component has a screening stage.
The separable fraction of the total mass flow is specified using the input RateA.
The flownet of the separated partial mass flow C is topologically not connected to the flownet
of the total mass flow AB. It must therefore be described using a separate NetParam block.
A separation can only take place when the flow network connected to the connector C is open.
During operation, at least the separable fraction must always be separated from the total mass
flow. If this fraction cannot be discharged using the flow network connected to connector C, the
main flow is reduced. The screen is blocked.
A corresponding flow coefficient of the screen (kVS value) is also required for the main mass
flow. If this flow coefficient is too small, the required mass flow may not be achieved.
The Rate output shows the percentage of the separable mixture component at output B. We
assume a complete separation in the Separator component so that this percentage is always
0%.
There is no backflow via the connector C. A backflow from B to A is also not possible.
A pressure drop is calculated in the component for the main mass flow. This pressure drop
depends on:
● Flow coefficient of the screen (kVS value)
● Throughflow (volume flow, medium)
The pressure drop across the screen is calculated according to the following formula:
ෙS P& VHF
EDU NJ K
N96
ˮ
P
Whereby:
NOTICE
The flow network of the discharged mass flow at connector C begins in the component with a
mass flow source.
Because of this mass flow source, the pressure reached at the edge of the flow network is
dependent on the separated-out mass flow and the pressure drop in the following branch.
Pressure drops that are too high in the following branch (for example too low kVS values in the
valves) can result in impossible physical states (e.g. pressure in the output is higher than in the
main flow).
Parameters
Operating window
The following variables for the following mass flows are displayed in the operating window:
● Incoming total mass flow
● Outgoing total mass flow
● Separated partial mass flow
See also
Geodetic height (Page 588)
Separator
Symbol
Function
The separator is used for partial or complete separation of a partial mass flow C (e.g. of a solid
matter mass fraction) from the main flow AB.
Because the flow network in SIMIT generally only permits the transport of gases and liquids,
solids are handled like liquids here. A pressure difference is therefore necessary for a solid
matter transport Conveyor equipment is replaced with equivalent connections that consist of
pumps, valves, sources and sinks.
The flow network of the separated-out partial mass flow C is topologically not connected to the
flow network of the main mass flow AB. The flow network of the partial mass flow must therefore
be described using a separate NetParam block.
A separation can only take place when the flow network connected to the connector C is open.
For example, if this flow network is blocked by a closed valve, this separator does not perform
any separation. In this case, the corresponding mass flow is forwarded to the output B.
A corresponding pressure drop is also required from the main mass flow to the connection point
C.
Backflow via the connector C is not possible.
Depending on the flow direction, the mass fraction of the partial mass flow to be separated is
specified using the input RateA or RateB.
A node is included in the Separator component. You can simulate a storage volume using the
dynamics of this node. You must make node settings separately for the main flow network and
the partial flow network using the corresponding network parameter assignment component
(NetParam).
0DLQIORZ 0DLQIORZ
6HSDUDWHGVROLG 6HSDUDWHGVROLG
PDWWHUIUDFWLRQ PDWWHUIUDFWLRQ
The main flow connectors A and B are designed identically. The partial mass flow to be
separated is always removed via the connector C .
The mass fraction of the main flow exiting at A or B is calculated and displayed at the output
Rate.
A pressure drop is calculated for the main mass flow. This pressure drop depends on:
● Pressure drop value of the separator (kVS value)
● Throughflow (volume flow, medium)
The pressure drop across the separator is calculated according to the following formula:
ෙS P& VHF
EDU NJ K
N96 ˮ
P
Whereby:
Parameters
Operating window
The following variables for the following mass flows are displayed in the operating window:
● Incoming main mass flow
● Outgoing main mass flow
● Separated partial mass flow
See also
Geodetic height (Page 588)
8.2.5.9 System
Symbol
Function
The BranchParam component type is used for parameter assignment of a branch in the flow
network. For this purpose, the component is inserted anywhere in the branch whose
parameters are to be assigned.
Parameters
Symbol
Function
The Mnode component type specifies the values for mass flow ṁ and specific enthalpy h at its
connector A. This type of component forms a boundary for the flow network. When looking at
the flow network as a graph, this corresponds to an inflow or outflow into an (internal) node or
branch. An internal node with defined inflow or outflow is added to the flow network for each
component of this type.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The NetParam component type is used for parameter assignment of a flow network. To do so,
the component is added at any location in any branch of the flow network.
Representation of the NetParam component depending on the set medium:
NOTICE
The component lets you switch the medium during runtime. However, this should only be done
in exceptional cases because, depending on the connection of the components, the model
may enter an undefined state.
Model crashes or reaching of undefined states may be possible.
If no component is used in a flow network for parameter assignment of a flow network, the
calculation is made with the defaults for water/steam.
Parameters
Additional parameters
Symbol
Function
The PHnode component type represents an option for closure of a flow network to the outside.
A fixed pressure p and the associated enthalpy h are specified as a boundary condition for the
flow network in the component.
When looking at the flow network as a graph, this component corresponds to an (external) node
for which the entered conditions are permanently specified.
Display
During the simulation, the selected medium is displayed in color in the symbol of the
component. The component receives the information required for this display from the
associated flow network parameter assignment (NetParam component).
Operating window
The following variables are displayed in the operating window:
Density r kg/m³
Temperature T °C
Specific enthalpy h kJ/kg
1
For outflow ṁ > 0, for inflow ṁ < 0.
Symbol
Function
The PTnode component type represents an option for closure of a flow network to the outside.
A fixed pressure p and the associated temperature T are specified as a boundary condition for
the flow network in the component.
When looking at the flow network as a graph, this component corresponds to an (external) node
for which the entered conditions are permanently specified.
Note
Please note that you cannot enter a state in the two-phase area with the medium "Water/
Steam". The state is either completely liquid or completely vaporous depending on the
temperature and pressure. If the boiling point is entered at the relevant pressure, the state is
completely gaseous.
If you want to specify a state in the two-phase area, you will need to use component
type PHNode.
Display
During the simulation, the selected medium is displayed in color in the symbol of the
component. The component receives the information required for this display from the
associated flow network parameter assignment (NetParam component).
Representation of the PTnode component depending on the set medium:
Operating window
The following variables are displayed in the operating window:
Density r kg/m³
Temperature T °C
Specific enthalpy h kJ/kg
8.2.5.10 Tanks
Agitator
Symbol
Function
The Agitator component type exists to emulate the presence and operation of an agitator. The
agitator is switched on via the Speed connector. The rotation of the agitator is shown
graphically at a Speed > 0.
However, this component has no effect on mixing in a stirring tank because stirring tanks are
always assumed to be perfectly mixed systems.
This component also has no effect on the heat transfer from a heating element to a stirring tank.
To model the heat transfer, you must link the agitator speed with the HeatingJacket component.
Symbol
Function
The DrumWS component type provides the simulation of a water/steam drum that is closed off
from the environment.
The closed drum is assumed to be a horizontal or vertical cylindrical tank whose inflows and
outflows are via connectors N1 .. Nn. A throttling action is assumed for each connector
according to the following formula:
ෙS P& VHF
EDU NJ K
N96
ˮ
P
The installation height of the individual connectors is specified for each connector with the
ConnectorHeight parameter vector. The type of each connector (inlet or outlet, water or steam)
is defined dynamically during the simulation and depends on the thermodynamic states in the
drum, the configured geometry (ConnectorHeight, Orientation) and the respective boundary
conditions.
You can move the connectors as needed along the outline of the component symbol with the
mouse while pressing the <Alt> key.
An immediate separation of the medium into two homogeneous saturated phases is assumed
in the drum: the saturated liquid phase and the saturated vapor phase. Only connectors to
water/steam-type flow networks are included in the balance calculation. Connectors to other
types of flow networks (gas, liquid or user-specific media) are not balanced.
This way you obtain the mass of water and steam in the tank that is balanced using the mass
flows according to
Q
GP
GW
P& L
L
or due to
m = ρV
the change of the average density to
Q
Gˮ
9
GW
P& L
L
Q
G KP
GW
K P& L L
L
Whereby h is the specific enthalpy (mean enthalpy) of water/steam in the drum and hi is the
specific enthalpy of the inflow and outflow at the i-th connector. For outflows, the specific
enthalpy of the medium in the drum is to be used, which means h' for outflows of saturated
water, h" for outflows of saturated steam. The balancing is calculated as follows
Q Q Q
GK
P
GW
KL K P& L Kಿ K P& L Kಿಿ K P& L
L L ෛ = L L ෛ $ಿ L L ෛ $ಿಿ
In this case, the inflows Z, outflows of saturated water A' and outflows of saturated vapor A" are
added up.
To model a heat exchange with the ideally insulated tank, the enthalpy balance is added
according to
Q Q Q
GK
P
GW
KL K P& L Kಿ K P& L Kಿಿ K P& L $ ˞ 77 76
L L ෛ = L L ෛ $ಿ L L ෛ $ಿಿ
TT is the temperature of the tank wall, TS the saturation temperature of water/steam.
The heat storage in the tank wall is described with the heat balance:
G77
$ ˞ 76 77
GW P7 F7
+
P : ุ 9PLQ ˮ PLQ
The required increase can be set with the hysteresis Hmin.
A corresponding note is shown in the symbol of a component for an empty drum (see figure).
+
P : ื ˮ9 ˮ9PLQ PLQ
The required decrease can be set with the hysteresis Hmin.
A corresponding note is shown in the symbol of a component for a full drum (see figure).
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
See also
Geodetic height (Page 588)
Symbol
Function
The electrical heating jacket is an add-on to the StorageTankLiquid. The heating power at input
Q_In is supplied as heat flow Q to the tank. The heat flow is specified in kW.
The component is used to visualize the heating jacket in the SIMIT chart. For simulation
purposes, the heating power can also be connected directly to a StorageTankLiquid.
Unlike with the HeatingJacket component, the influence of the agitator speed or of the tank level
is not taken into consideration here.
This component does not have parameters or an operating window.
Symbol
Function
The Flash component describes a 2-phase separator and is used to distribute the content into
a liquid and gas phase. Depending on the temperature and pressure, the phase equilibrium is
established between the low boiler (LB = Low Boiling) and the high boiler (HB = High Boiling).
The incoming and outgoing material flows are hereby automatically balanced regarding mass
and enthalpy. Tempering of the mass stored in the tank is possible by means of a direct input
or various additional components.
The phase equilibrium is parameterized over the normal boiling temperature (at 1 bar) of the
low and high boiler (TS_LB, TS_HB) as well as over their vaporization enthalpies (hv_LB,
hv_HB). The size of the boiling lens can be varied using the S parameter. This means:
● S = 0, maximum size of the boiling lens (see figure)
● S = THB − TLB, no boiling lens (makes no sense physically)
It is assumed that there is an equal pressure dependency of the boiling points for both
materials. This is parameterized with the boiling temperature of the high boiler (T2_HB) for
another (preferably higher) pressure (p2_HB).
7HPSHUDWXUH>r&@
7HPSHUDWXUH>r&@
0DVVIUDFWLRQKLJKERLOHU 0DVVIUDFWLRQKLJKERLOHU 0DVVIUDFWLRQKLJKERLOHU
>NJNJ@ >NJNJ@ >NJNJ@
Tau line
Boiling point curve
Figure 8-73 Boiling lens as a function of the parameter S (spread)
3UHVVXUH>EDU@
SB+%
SB+% 7B+%
7B+%
7HPSHUDWXUH>r&@
Figure 8-74 Dependency of the boiling temperature on the pressure
Circuit
The N1 ..Nn connectors are the connection points for the material flows, which means for the
connection of pipelines. The number of these connection points depends on the system to be
simulated and is specified with the NbrOfConnectors parameter. All connectors of the input
vector N1..Nn are initially equal and can be used for all connector types (water/steam, ideal
gas, liquid).
The material medium in the neighboring flow networks is defined over the NetParam
component. All defined inputs must be interconnected in the input vector N1 ..Nn. These inputs
must not remain open during simulation because this will create open flow networks. This
would, in turn, result in an error message during code generation.
For the water/steam connector type, the incoming medium is mixed internally in the tank with
a liquid medium. The incoming mass and enthalpy is taken into consideration.
A flash typically has three connectors. The feed comes in through the first connector. At the
second connector on the top of the tank, the gas flow is removed. At the third connector at the
bottom of the tank, the liquid drain is connected.
At least one gas flow must be connected to the flash.
Parameter ConnectorHeight
The installation height of the connecting pipe at the flash is required for each of the connection
points N1..Nn (ConnectorHeight parameter). The information is entered in meters. The default
setting is 0 m, which means at the bottom of the tank. Negative values are permitted for the
simulation of connectors at a lower position. If a gas connector is located below the fill level of
the tank, neither liquid nor gas can flow out through this connector from the tank. However, the
inflow of gas is possible.
Alignment
The Flash component can be operated as vertical or horizontal tank. The alignment can be set
with the Position parameter. The tank is simulated as either vertical or horizontal cylinder. In
case of a vertical flash, the HeightOrLength parameter indicates the height of the tank; for a
horizontal flash, it indicates the length.
Balancing of the states is stopped for an empty flash, which means changes to the total mass,
component mass and specific enthalpy are discarded. The "empty" state continues until there
is a sufficient increase in the amount of liquid. A corresponding indicator for an empty tank is
shown in the component symbol (see figure).
Parameter
Additional parameters
Operating window
Symbol
Function
The HeatingJacket component is optimized for use in combination with a StorageTankLiquid.
It represents an add-on component for the StorageTankLiquid but can also be used in
combination with the pressure strainer or on its own.
4& N $ ෙ7
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The StorageTankLiquid component type is used for mixing and storage of liquid media. The
incoming and outgoing material flows are hereby automatically balanced regarding mass and
enthalpy.
The temperature of the substance stored in the tank can be adjusted by means of a direct input
or different additional components.
If there are gas connectors, these are balanced separately and form a pressure padding above
the liquid in the tank.
The mass balanced in the tank is a mixture of up to two liquid components. The concentration
of these components in the inflows can be specified at each input.
A thermal separation of the two components is possible during the simulation. These
components are therefore referred to in the following as lower boiling and higher boiling
components.
Other physical processes, such as the mixing of concentrations, are also possible.
Circuit
The connectors N1 ..Nn serve as connection points for substance flows, which means for
connection of pipelines.
The number of these connection points depends on the system to be simulated and is specified
with the NbrOfConnectors parameter. All connectors of the input vector N1..Nn are initially
equal and can be used for all connection types (water/steam, ideal gas, liquid).
Parameter ConnectorHeight
For each of the connection points N1..Nn, the installation height of the connection pipe on the
tank (ConnectorHeight parameter) is needed. The information is entered in meters. The default
is 0 m, which means at the bottom of the tank. Negative values are permitted for simulation of
connectors at a lower position. If a gas connection is below the fill level of the tank, neither liquid
nor gas can flow out of the container through that connection.
Q
GP/LTXLG
GW P& /LTXLGL P
& (YDS
L
Q
GP(YDS)UDFWLRQ
GW P& (YDS)UDFWLRQL P
& (YDS
L
GK/LTXLG Q
GW P/LTXLG
P
& /LTXLGL K/LTXLGL 4& P
& (YDS Kಿ ෙ+9
L
K/LTXLG
7/LTXLG
F3
Q
GP*DV
GW P& *DVL P
& (YDS
L
GK*DV Q
GW P*DV
P & (YDS Kಿ ෙ+9
& *DVL K*DVL P
L
The gas pressure is then calculated according to the state equation of ideal gases:
P*DV 56 7*DV
S*DV
9*DV
The gas temperature TGas is calculated from the balanced gas enthalpy hGas. If the gas
temperature and liquid temperature are different, a corresponding temperature equalization
occurs during simulation.
If a gas connector is not connected, the gas balance calculation does not take place. In this
case, the gas pressure is replaced with the atmospheric pressure. In this case we assume that
the tank is open to the surrounding environment.
Representation of the balancing in the storage tank with and without gas fraction:
Alignment
The StorageTankLiquid component can be operated as either a vertical or a horizontal tank.
The alignment can be set with the Position parameter. The tank is then simulated as a vertical
or horizontal cylinder. The HeightOrLength parameter specifies the height of vertical tanks and
the length of horizontal tanks.
Evaporation
If the stored liquid contains a lower boiling component, it is possible to evaporate it. To do this,
the liquid mixture must be heated to a temperature above the boiling point corresponding to the
current pressure. The steam pressure curve needed for this is configured using the Boiling
parameter (steam pressure curve of the lower boiling component pS = ƒ (TS) in [bar]).
In addition, the vaporization enthalpy of the lower boiling component must be specified as a
characteristic curve (ΔHV = ƒ(TS) in [kJ/kg]) using the Vaporization parameter.
The respective characteristic curves for water are used by default. They can be edited within
the charts or imported from a text file.
Examples of these characteristic curves are shown in the figures below:
36 ෙ+9
76 76
Figure 8-80 Example for vaporization enthalpy and steam pressure curve
When the vaporization condition T > TS (pS) has been reached, the lower boiling component
gradually transforms to the gas phase and is added to the gas balance space. No provision is
made for condensation in the tank.
For this, you must first enter the setpoint in the corresponding digital input SetValues and apply
it with the "Set" button. The state "stored mass" can be specified using the value of the mass
as well as using the fill level (Level).
By manipulating state variables in this way, you can, for example, speed up heating processes
or filling processes. Likewise, you can empty the tank, for example, to return to an earlier step
in a step sequence.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
See also
Geodetic height (Page 588)
8.2.5.11 Valves
Symbol
Function
The component types ControlValve, Valve and AngleValve are used to simulate a control
valve. They can also be used for butterfly valves, plug valves or gate valves.
The listed components differ only in their symbols. The behavior of the components is identical.
Depending on the valve position, the configured characteristic curve and the valve size (kVS
value), the pressure drop across the valve is calculated according to the formula below.
ෙS P& VHF
EDU NJ K
N96 ˮ
Whereby:
Parameters
Additional parameters
Operating window
You can switch between automated control (control using the actuator/sensor level) and
manual control in the operating window. The default is always automated control.
The following variables are displayed in the extended operating window:
Symbol
Function
The RuptureDisc component type simulates the functionality of a rupture disc. Depending on
a configurable rupturing pressure, a diaphragm is irrevocably damaged or, from a simulation
point of view, a valve is irreversibly opened.
However, you can manually close the rupture disk again in the simulation model after it has
ruptured with the "Reset" button in the operating window. This function is needed in order to test
the rupturing of the rupture disc several times in succession without having to reset the
simulation.
You can make use of this function only as a manual function via the operating window. It cannot
be connected to other components or the control technology.
For simulation purposes, the rupture disc is simply considered to be a closed valve that opens
permanently when the rupturing pressure is exceeded. The parameter assignment is therefore
the same as for a valve.
Parameters
Additional parameters
Operating window
You can reset the rupture disk in the operating window.
The following variables are displayed in the extended operating window:
During the simulation, the operating states of the RuptureDisc component are visualized in the
symbol:
Connection example:
In this connection example, a rupture disc is connected upstream from a safety valve. It is
important in this case that the kV0 value of the downstream safety valve is significantly greater
than the kV0 value of the rupture disc.
Symbol
Function
The StopValve component type is used for simulation of a check valve. The pressure drop
across the check valve is calculated depending on the direction of flow. The reference direction
is defined for the mass flow ṁ from connector A to connector. This means ṁ > 0 for mass flow
in the reference direction.
For a positive media flow, the valve is simulated as a fully opened valve. For a negative media
flow, the component type represents a closed valve. In this case leakage becomes active; the
valve coefficient kV therefore corresponds to the minimum opening kV0.
Parameters
Additional parameters
To realize the check function, the valve characteristic value kV0 must be selected sufficiently
small.
Operating window
The following variables are displayed in the operating window:
SafetyValve / AngleSafetyValve
Symbol
Function
The components SafetyValve / AngleSafetyValve are used as a safety valve. For a
configurable pressure difference between the connectors A and B, the valve is also opened in
a configurable time. The valve remains open as long as the pressure difference exists. The
valve is closed automatically as soon as the pressure difference has dropped below the
configured opening pressure minus the configured hysteresis.
9DOYH
/LIW
S>EDU@
+\VWHUHVH 2SHQLQJ
'HOWD3 3UHVVXUH
Figure 8-88 Opening and closing behavior of the safety valve
The model of the safety valve is designed with protection against polarity reversal; flow through
the valve in both directions is permitted. For calculation of the pressure difference, the side on
which the higher pressure exists is immaterial. This means that the safety valve cannot be
inadvertently inserted in the wrong direction in the model (e.g. as the result of an automatic
generation).
Note, however, that a preferred direction of flow from A to B is defined within the valve. If the
flow takes place in this direction, a positive mass flow is displayed in the operating window. If
the flow is in the opposite direction (i.e. the valve is mirrored, for example), this mass flow is
negative. The pressure drop Δp is also negative or positive depending on the flow direction.
Parameters
Additional parameters
During the simulation, the operating states of the component are visualized in the symbol.
To do this, the valve position is displayed as shown in the figure below.
Operating window
The safety valve can also be opened or blocked manually in the operating window using the
"local control" function. This gives you the ability to easily simulate a malfunction of the safety
valve.
For manual control, you can specify the valve position using a slider. In this case the function
is that of a manual valve. The dependency on the pressure drop no longer exists.
ThreeWayValve
Symbol
Function
The ThreeWayValve component type is used for simulation of a three-way valve. Depending
on the valve position, the flow paths shown in the figure below can be opened.
The component type has two flow branches. Flow is always present in connector AB. It is the
connector that is shared by both valve branches. Depending on the valve position, connector A
or connector B can be open (intermediate positions are possible). No flow is possible from A to
B or vice versa (analog to the real three-way valve).
Depending on its insertion, the component can be used as mixing valve or as diverting valve.
The anticipated flow in the valve (mixing valve or diverting valve) must already be known when
the connection is made. Insert the valve in the corresponding orientation.
The flow direction during the simulation results from the relative pressures.
The valve position is specified at the Position input. This value refers to the valve branch AB–A.
Opening of the valve branch AB–B results from the difference of the opening of the valve branch
AB–A at 100%.
The pressure drop above the valve is calculated using the following formula depending on the
valve position, the configured characteristic and the valve size (kVS value):
ෙS P& VHF
EDU NJ K
N96
ˮ
P
This calculation is made for both valve branches. The following applies, for example, to the
branch AB–A:
Parameters
Additional parameters
Operating window
You can switch between automated control (control using the actuator/sensor level) and
manual control in the operating window. The default is always automated control.
For manual control, you can specify the valve position using a slider. The slider value hereby
refers to the branch AB–A.
The following variables are displayed in the extended operating window:
Valve
Symbol
Function
The Valve component type is used for simulating a control valve. Depending on the control
valve position the pressure drop over the control valve is calculated as
ෙS P& VHF
EDU NJ K
N9 ˮ
P
. The following applies:
● ∆p = pB − pA is the pressure drop over the valve in bar
● P
& is the mass flow in kg/s
● ρ is the density of the medium in kg/m³
● kV is the flow coefficient in m3/h
The reference direction is defined for the mass flow P
& from connector A to connector B, which
means it is P
& ! for mass flow in the reference direction. The pressure drop therefore has a
negative value: ∆p < 0.
At the Position connector, the H position of the valve drive is given as a percentage for which
the drive component types of the SIMIT basic library, for example, can be used.
This position value is limited to the range 0 ≤ H ≤ 100%. The control valve position is mapped
using the control valve characteristic to the flow coefficient kV. The following applies
N9 +
N9 69 69
for a linear characteristic,
N9 +
N9 69 69
for a quadratic characteristic,
+
N9
69
N9
for an equal percentage characteristic.
N9
69
N9
is applied here as a quotient consisting of the flow coefficient cV100 for a completely open value
(H = 100 %) and the flow coefficient kV0 for a completely closed valve (H = 0).
Any valve characteristic curves can be created with the Characteristic component type from the
SIMIT basic library. The characteristic component is simply placed upstream of the valve
Position input.
The linear characteristic is then configured at the control valve so that the characteristic
specified with the characteristic component is simply scaled with the factor (kV100 – kV0) / kV0 and
offset by kV0.
Parameters
Additional parameters
If ShowFlow is set to True , the valve position is displayed as shown in the figure below.
If ShowFlowDirection is also set to True, the valve position and direction of flow are displayed
as shown in the figure below.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The StopValve component type is used for simulation of a check valve. Depending on the flow
direction the pressure drop over the control valve is calculated as
P & VHF
IRU P
& !
NJ K
N9 ˮ
ෙS P
EDU P &
VHF
NJ
IRU P
&
K
N9 ˮ
P
. The following applies:
● ∆p = pB − pA is the pressure drop over the non-return valve in bar,
● P
& is the mass flow in kg/s,
● p is the density of the medium in kg/m3 and
● kV is the flow coefficient in m3/h.
The reference direction is defined for the mass flow P
& from connector A to connector B, which
means it is P ! for mass flow in the reference direction.
&
Parameters
In order to implement the non-return function, the flow coefficient kV0 must be sufficiently small.
Pump – pump
Symbol
Function
The Pump component type calculates the pressure increase as a function of flow rate and
speed according to the following formula:
Q ෙS ෙS
ෙS
P
&
ෙS IRU P
& !
P&
Whereby:
The quadratic relation between pressure boost and flow defined above is illustrated in the figure
below for operation of the pump in the normal range, which means for P & ! , ∆p > 0 .
3UHVVXUHERRVW ˂S
˂S
P
˂S
&
Q
Q ˂S
)ORZ P
&
QP& P
&
Q ෙS ෙS
ෙS
P&
ෙS IRU P
&
N P&
when the flow is reversed ( P& ). The throttling effect can be influenced by means of the flow
coefficient k. The figure below shows the extended characteristic qualitatively for various
characteristic values k:
3UHVVXUHERRVW
)ORZ
N
N
N
.
It is clear that the throttling effect is greater for smaller values of the flow coefficient k.
To stabilize a simulation that contains a component of this type, pressure reversal (∆p < 0) is
also calculated using the above equations. For switched off pumps, which means for zero
speed, this results in pure throttling for the flow in pump direction as well as for the flow against
pump direction:
ෙ S
ෙ S P&
IRU P
&
N P&
ෙS
ෙ S
ෙ S P
&
IRU P
& !
P&
Parameters
Additional parameters
If the additional parameter Showflow is set to True, the operating state in shown in the pump
symbol.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The Pnode component type specifies the values for pressure p and specific enthalpy h at its
connector A. This type of component forms a boundary for the flownet. When the flownet is
represented as a graph, it corresponds to an (external) node for which the pressure and specific
enthalpy are predefined.
Operating window
The following variables are displayed in the operating window:
For outflow P
& ! , for inflow P
& .
Symbol
Function
The Mnode component type specifies the values for mass flow P & and specific enthalpy h at its
connector A. This type of component forms a boundary for the flow network. When looking at
the flow network as a graph, this corresponds to an inflow or outflow into an (internal) node or
branch. An internal node with defined inflow or outflow is added to the flow network for each
component of this type.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The NetParam component type is used for flow network parameter assignment. To do so, the
component is added at any location in any branch of the flow network.
Parameters
Additional parameters
Symbol
Function
The BranchParam component type is used for branch parameter assignment in the flow
network. The components are placed anywhere along the branch to be assigned parameters.
Parameters
Joint – joint
Symbol
Function
With the component type Joint, three branches connected to its connectors A, B and C can be
combined in a node. An internal node is added to the flow network with the component Joint .
Operating window
The following variables are displayed in the operating window:
Symbol
Function
With the component type JointParam, three branches connected to its connectors A, B and C
can be combined in a node. An internal node is added to the flow network with the
component JointParam .
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Components for simulating measurements in pipeline networks can be found in the MEASURE
directory.
Connectors of the Measure connection type are used in the measuring components. The
meaning of the individual signals for this type are given in the following table.
Symbol
Function
The PipeMeasure component type forms a measuring point in the tube. It is inserted with its
connectors A and B at the desired measuring point in the flownet. The measuring process for
the various variables is not simulated with suitable models; the variables calculated by the
flownet solution procedure are output.
The measured variables are output over the Measure connector:
● absolute value _P
& _ of the flow rate value,
● Pressure pA at connector A and
● Temperature T.
All other signals of connector Measure are not set.
When the simulation is running, the direction of the medium flow is indicated by an arrow on the
symbol.
Operating window
The following variables are displayed in the operating window:
Temperature T °C
Symbol
Function
Component type MeasureAll returns the measured values bundled over measuring
input Measure as individual signals at its outputs: pressure, temperature, flow, level and weight.
This type of component can be connected to the pipe measuring point, for example, and
thereby output its measurement variables as individual signals.
Operating window
The following variables are displayed in the operating window:
Level l m
Weight M kg
Symbol
Function
The FlowIndicator component type displays the flow specified using its Measure input.
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The LevelIndicator component type displays the level specified using its Measure input.
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The PressureIndicator component type displays the pressure specified using its Measure input.
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The TemperatureIndicator component type displays the temperature specified using
its Measure input.
Operating window
The following variable is displayed in the operating window:
Symbol
Function
The WeightIndicator component type displays the weight specified using its Measure input.
Operating window
The following variable is displayed in the operating window:
Component types that can be used in the flownet with the water/steam medium are located in
the MEDIUM\WATER.STEAM folder of the FLOWNET library. The medium parameter for a
flownet that contains these components must be set to the value "Water/Steam".
Symbol
Function
The NetWS component type is used for parameter assignment for a water/steam network. To
do so, the component is added at any location in any branch of the flow network.
Parameters
Additional parameters
Symbol
Function
The PnodeWS component type specifies the values for pressure p and specific enthalpy h at
its connector A. This type of component forms a boundary for the flownet. When the flownet is
represented as a graph, it corresponds to an (external) node for which the pressure and specific
enthalpy are predefined.
Operating window
The following variables are displayed in the operating window:
Density r kg/m³
Temperature T °C
Specific enthalpy h kJ/kg
For outflow P
& ! , for inflow P
& .
Symbol
Function
The MnodeWS component type specifies the values for mass flow P & and specific enthalpy h
at its connector A. This type of component forms a boundary for the flow network. When looking
at the flow network as a graph, this corresponds to an inflow or outflow into an (internal) node
or branch. An internal node with defined inflow or outflow is added to the flow network for each
component of this type.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
With the component type JointWS, three branches connected to its connectors A, B and C can
be combined in a node. An internal node is added to the flow network with the
component JointWS.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
With the component type JointParamWS, three branches connected to its connectors A, B
and C can be combined in a node. An internal node is added to the flow network with the
component JointParamWS.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The StorageTankWS component type provides the simulation with an open water tank, which
means a tank that is not sealed from the environment.
Inflows and outflows occur via the STUBx connectors on the tank. For each of the N connectors,
a throttling effect defined by
ෙS P & VHF
EDU NJ K
N9 ˮ
P
is assumed. The tank can have a minimum of one and a maximum of 16 connectors. The
connectors can be moved to any position on the outline of the component symbol by using the
mouse while simultaneously pressing ALT.
It is assumed that the water in the tank is immediately completely mixed, which means a
homogenous medium with an overall consistent density and enthalpy in the tank.
The inflows and outflows of water are balanced across the N connectors of the tank. The
balanced mass M of the N flow rates P & L of the medium in the tank is thus defined by
G0 1
GW P& L
L
The water volume balancing via the volume flows results in the rate of change of density ρ given
by
1 1
Gˮ ˮ
GW 0
P& L ˮ P&
ˮL L
L L ෛ = L L ෛ =
1 1
GK
GW 0
KL P& L K P&
ˮL L
L L ෛ = L L ෛ =
+
0 ุ 9PLQ ˮ PLQ
is checked. The required increase can be set with the hysteresis Hmin. A corresponding indicator
for an empty tank is shown in the component symbol.
Note
It is not checked whether the state variables (pressure, enthalpy) for the inflows and tank
contents always have values for the water state.
In the simulation, inflows specified accordingly may result in a situation where the state values
for the tank contents describe a water-steam mixture or pure steam, which has no physical
meaning.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The DrumWS component type provides the simulation with a drum, which means a closed
container for water/steam that is sealed off from the environment.
The drum is assumed to be a cylindrical, horizontal or vertically standing container, whose
inflows and outflows occur via the STUBWx and/or STUBSx connectors. For each of the
connectors, a throttling effect defined by
ෙS P & VHF
EDU NJ K
N9 ˮ
P
is assumed. At the NW connectors STUBWx, medium with the state variables of the saturated
water can be drawn out and medium with the state variables of saturated steam can be drawn
out at the NS connector STUBSx. The drum can have a minimum of one and a maximum of eight
connectors of each type. The connectors can be moved to any position on the outline of the
component symbol by using the mouse while simultaneously pressing ALT.
It is assumed that the medium in the drum immediately separates into two homogenous
saturated phases: the saturated liquid phase and the saturated vapor phase.
The inflows and outflows of water/steam are balanced via the N = NW + NS drum connectors.
This results in a mass of water and steam in the drum, balanced via the mass flows, given by
G0 1
GW P& L
L
or given
M = ρV
the change of the average density to
Gˮ 1
9
GW P& L
L
G K0 1
GW K P& L L
L
Whereby h is the specific enthalpy (mean enthalpy) of water/steam in the drum and hi is the
specific enthalpy of the inflow and outflow at the i-th connector. The specific enthalpy of the
medium in the drum must be applied for outflows, which means h'' for outflows of saturated
water and h" for outflows of saturated steam. The balancing is calculated as follows
GK 1 1 1
0
GW KL K P& L Kಿ K P& L Kಿಿ K P& L
L L ෛ = L L ෛ $ಿ L L ෛ $ಿಿ
Whereby the inflows Z, outflows of saturated water A' and/or outflows of saturated steam A" are
summed.
In order to model a heat exchange with an ideally insulated drum, the enthalpy balance
equation is extended as follows
GK 1 1 1
0
GW KL K P& L Kಿ K P& L Kಿಿ K P& L $ ˞ 77 76
L L ෛ = L L ෛ $ಿ L L ෛ $ಿಿ
TT is the temperature of the drum wall, TS is the saturation temperature of water/steam.
The heat storage in the drum wall is described by the heat balance
G77
$ ˞ 76 77
GW 07 F7
.
The water level l, the saturation temperature TS, the saturation pressure pS and the mass M of
water/steam are output at the Measure connector.
The STUBWx connectors are assumed to be located at the bottom of the drum. The pressure
at these connectors therefore is the sum
p = p'gl + pS
of the saturated steam and the hydrostatic pressure of the water.
+
0 : ุ 9PLQ ˮ PLQ
is checked. The required increase can be set with the hysteresis Hmin. A corresponding indicator
for an empty drum is shown in the component symbol.
+
0 : ื ˮ9 ˮ9PLQ PLQ
is checked. The required decrease can be set with the hysteresis Hmin. A corresponding
indicator for a full drum is shown in the component symbol.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The ElectricalHeaterWS component type is used for simulation of an electric heat exchanger.
The electrical heating power Pel is specified in kW with connector ElectricalPower.
Water/steam is directed via the TS_IN and TS_OUT connectors as a heated medium. The flow
P
& is throttled according to the relationship
ෙS P
& VHF
EDU NJ K
N9 ˮ76
P
with throttle coefficient kV. The reference direction for the flow is chosen as from TS_IN to
TS_OUT.
For the heat transfer, a simple one tube model divided into segments is applied. The number N
of segments can be set to a value between 4 and 16.
P
& K +76 +7 3HO
76 76
+76 +7
... ...
+761 +71
① Tube side
② Tube
It is assumed that the supplied electrical energy is completely converted into heat. The heat
balance for a segment i of the spare tube with extremely simplified heat transfer is then given
by
G77L
D7 3HO E7 776L 77L
GW
with
$ 76 ˞76
D7 E7
07 F7 07 F7
In addition, the water/steam-side enthalpy balancing for a segment i is described by
GK76L
D76 K76 L K76L E76 77L 776L
GW
with
Parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The HeatExchangerWS component type is used for simulation of a heat exchanger for water/
steam at the tube and shell side. The simulation is implemented for the three types:
● Parallel-flow heat exchanger
● Counter-flow heat exchanger
● Cross-flow heat exchanger
Both media are routed on the tube side via the connectors TS_IN and TS_OUT, and on the shell
side via the connectors SS_IN and SS_OUT.
The flow P
& is throttled on the tube side and shell side according to the relationship
ෙS P & VHF
EDU NJ K
N9 ˮ
P
with the relevant throttle coefficient kv. The chosen reference direction for the flow is from
connector _IN to _OUT on the tube side and shell side.
For the heat transfer, a simple one tube model divided into segments is applied. The number N
of segments can be set to a value between 4 and 16.
① Tube-side space
② Tube
③ Shell-side space
The water/steam heat on the tube and shell side and the heat in the tube itself are balanced.
4& 776
7XEH 77
4& 667
4& 66LQ 4& 66RXW
6KHOOVLGHPHGLXP K66 766
The two heat transfers, from the shell side medium to the tube and from the tube to the tube side
medium, are set according to
GK76L
D76 K76 L K76L E76 77L 776L
GW
G77 L
D7 766 L 77 L E7 776 L 77 L
GW
GK66 L
D66 K66 L K66 L E66 77L 766 L
GW
apply with the following coefficients, which are the same for all segments:
1P & 76 $76 ˞76 1P & 66 $66 ˞66 $66 ˞66 $76 ˞76
D 76 E76 D66 E66 D7 E7
ˮ76976 ˮ76976 ˮ66966 ˮ66966 0 7 F7 07 F7
The values set for the media in the shell side and tube side of the flownet apply to the densities
ρTS, ρSS and the specific heat capacities cTS, cSS.
For initialization, the temperatures of the tube segments are set to the temperature of the tube-
side medium, calculated on the basis of the pressure (input FNTS.PRESSURE) and the
specific enthalpy (input FNTS.HSPEC).
Parameters
Operating window
The following variables are displayed in the operating window:
Component types that can be used in the flownet with the liquid medium are located in the
directory MEDIUM\LIQUID of the FLOWNET library. The medium parameter for a flownet that
contains these components should be set to the value "Liquid", if applicable.
Symbol
Function
The NetLiquid component type is used for parameter assignment for a liquid network. To do so,
the component is added at any location in any branch of the flow network.
Parameters
Additional parameters
Symbol
Function
The PnodeLiquid component type specifies the values for pressure and temperature at its
connector. It forms a boundary for the flownet to which it is connected. When you look at the
flow network as a graph, PnodeLiquid represents an (external) node for which the pressure and
temperature specifications are fixed.
Operating window
The following variables are displayed in the operating window:
Density r kg/m³
Temperature T °C
For outflow P
& ! , for inflow P
& .
Symbol
Function
The MnodeLiquid component type specifies the values for mass flow and temperature at its
connector. It forms a boundary for the flownet to which it is connected. When you look at the
flow network as a graph, MnodeLiquid represents an inflow or outflow into an (internal) node or
branch. Thus an internal node with a defined inflow or outflow is added to the flownet.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
With the component type JointLiquid, three branches connected to its connectors can be
combined in a node. All connectors are equal. An internal node is added to the flow network with
the component JointLiquid.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
With the component type JointParamLiquid, three branches connected to its connectors can be
combined in a node. All connectors are equal. An internal node is added to the flow network with
the component JointParamLiquid. This node can be assigned parameters.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The StorageTankLiquid component type provides the simulation with an open tank for liquids,
which means a tank that is not sealed from the environment.
Inflows and outflows occur via the STUBx connectors on the tank. For each of the N connectors,
a throttling effect defined by
ෙS P & VHF
EDU NJ K
N9 ˮ
P
is assumed. The tank can have a minimum of one and a maximum of 16 connectors. The
connectors can be moved to any position on the outline of the component symbol by using the
mouse while simultaneously pressing ALT.
It is assumed that the liquid in the tank is immediately completely mixed, which means it is a
homogenous medium with an overall consistent density and temperature.
The inflows and outflows are balanced across the N connectors of the tank. The balanced mass
M of the N mass flows P & L of the liquid in the tank, is defined by
G0 1
GW P& L
L
The temperature of the liquid is balanced as a mixing temperature from the inflows (i ∈ Z)
according to
1 1
G7
GW 0
KL P& L 7 P&
ˮL L
F/ L L ෛ = L L ෛ =
.
The dynamic behavior of the liquid in the tank is described by these balances for mass M and
temperature T.
The calculated variables for the level l of the liquid in the tank, its mass M and temperature T as
well as pressure p0 on the tank base are output at the Measure connector. The pressure p on
the tank base is calculated from the weight pressure ρgl of the liquid and the atmospheric
pressure pU according to
p = pU + ρgl
+
0 ุ 9PLQ ˮ PLQ
is checked. The required increase can be set with the hysteresis Hmin. A corresponding indicator
for an empty tank is shown in the component symbol.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The ElectricalHeaterLiquid component type is used for simulation of an electric heat
exchanger. The electrical heating power Pel is specified in kW with connector ElectricalPower .
The liquid is directed via the connectors TS_IN and TS_OUT as a heated medium. The flow P
&
is throttled according to the relationship
ෙS P& VHF
EDU NJ K
N9 ˮ
P
with throttle coefficient kV. The reference direction for the flow is chosen as from TS_IN to
TS_OUT.
For the heat transfer, a simple one tube model divided into segments is applied. The number N
of segments can be set to a value between 4 and 16.
PF
& 7 +/ +7 3HO
/ /
+/ +7
... ...
+/1 +71
① Tube side
② Tube
It is assumed that the supplied electrical energy is completely converted into heat. The heat
balance for a segment i of the spare tube with extremely simplified heat transfer is then given
by
G77L
D7 3HO E7 7/L 77L
GW
with
$˞
D7 E7
07 F7 07 F7
In addition, the heat balance of the liquid in a segment i is given by
G7/ L
D 7/ L 7/ L E 77L 7/ L
GW
with
1P& $˞
D E
ˮ9 F/ ˮ 9
TT,i and TL,i are the temperatures of the tube segment and the liquid in the segment i. The values
of the flow network apply for the density ρ and the specific heat capacity cL of the liquid.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The HeatExchangerLiquid component type is used for simulation of a heat exchanger for
liquids at the tube and shell side. The simulation is implemented for the three types:
● Parallel-flow heat exchanger
● Counter-flow heat exchanger
● Cross-flow heat exchanger
Both media are routed on the tube side via the connectors TS_IN and TS_OUT, and on the shell
side via the connectors SS_IN and SS_OUT.
The flow P
& is throttled on the tube side and shell side according to the relationship
ෙS P
& VHF
EDU NJ K
N9 ˮ76
P
with the relevant throttle coefficient kv. The chosen reference direction for the flow is from
connector _IN to _OUT on the tube side and shell side.
For the heat transfer, a simple one tube model divided into segments is applied. The number N
of segments can be set to a value between 4 and 16.
① Tube-side space
② Tube
③ Shell-side space
The liquid heat on the tube and shell side and the heat in the tube itself are balanced.
7XEHVLGHPHGLXP 776
4& 76LQ 4& 76RXW
4& 776
7XEH 77
4& 667
4& 66LQ 4& 66RXW
6KHOOVLGHPHGLXP 766
The two heat transfers, from the shell side liquid to the tube and from the tube to the tube side
liquid, are set according to
G776L
D76 776 L 776L E76 77L 776L
GW
G77 L
D7 766 L 77 L E7 776 L 77 L
GW
G766 L
D66 766 L 766 L E66 77L 766 L
GW
apply with the following coefficients, which are the same for all segments:
1P & 76 $76 ˞76 1P & 66 $66 ˞66 $66 ˞66 $76 ˞76
D 76 E76 D66 E66 D7 E7
ˮ76976 ˮ76976 ˮ66966 ˮ66966 0 7 F7 07 F7
The values set for the liquid in the shell side and tube side of the flownet apply to the densities
ρTS, ρSS and the specific heat capacities cTS, cSS.
For initialization, the temperatures of the tube segments are set to the temperature of the tube
side medium, calculated from the specific enthalpy ( FNTS.HSPEC input).
Parameters
Operating window
The following variables are displayed in the operating window:
Component types that can be used in the flownet with the gas medium are located in the
directory MEDIUM\GAS of the FLOWNET library. The medium parameter for a flownet that
contains these components should be set to the value "Ideal Gas", if applicable.
Symbol
Function
The NetGas component type is used for parameter assignment for a gas network. To do so, the
component is added at any location in any branch of the flow network.
Parameters
Additional parameters
Symbol
Function
The PnodeGas component type specifies the values for pressure and temperature at its
connector. It forms a boundary for the flownet to which it is connected. When you look at the
flow network as a graph, PnodeGas represents an (external) node for which the pressure and
temperature specifications are fixed.
Operating window
The following variables are displayed in the operating window:
Density r kg/m³
Temperature T °C
For outflow P
& ! , for inflow P
& .
Symbol
Function
The MnodeGas component type specifies the values for mass flow and temperature at its
connector. It forms a boundary for the flownet to which it is connected. When you look at the
flow network as a graph, Mnode represents an inflow or outflow into an (internal) node or
branch. Thus an internal node with a defined inflow or outflow is added to the flownet.
Operating window
The following variables are displayed in the operating window:
For outflow P
& ! , for inflow P
& .
Symbol
Function
With the component type JointGas, three branches connected to its connectors can be
combined in a node. All connectors are equal. An internal node is added to the flow network with
the component JointGas.
Operating window
The following variables are displayed in the operating window:
Symbol
Function
With the component type JointParamGas, three branches connected to its connectors can be
combined in a node. All connectors are equal. An internal node is added to the flow network with
the component JointParamGas. This node can be assigned parameters.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The StorageTankGas component type provides the simulation of a gas tank.
Inflows and outflows occur via the STUBx connectors on the tank. For each of the N connectors,
a throttling effect defined by
ෙS P& VHF
EDU NJ K
N9 ˮ
P
is assumed. The tank can have a minimum of one and a maximum of 16 connectors. The
connectors can be moved to any position on the outline of the component symbol by using the
mouse while simultaneously pressing ALT.
It is assumed that the gas in the tank is immediately completely mixed, which means a
homogenous medium in the tank with an overall consistent density and temperature in the tank.
The inflows and outflows are balanced across the N connectors of the tank. The balanced mass
M of the N flow rates P& L of the gas in the tank, is defined by
G0 1
GW P& L
L
The specific enthalpy h of the gas is balanced from the inflows (i ∈ Z) according to
1 1
GK
GW 0
KL P& L K P& L
L L ෛ = L L ෛ =
.
The dynamic behavior of the gas in the tank is described by these balances for mass M and
specific enthalpy h.
At the connector Measure, the variables for pressure p, temperature
K
7
F*
and mass M of the gas are output. The pressure is calculated from the equation for ideal gas:
56 7 . 0
S
3D
9 ຘ
EDU
+
0 ุ 0 PLQ PLQ
is checked. The required increase can be set with the hysteresis Hmin. A corresponding indicator
for an empty tank is shown in the component symbol.
+
ෙ0 ุ 0 PLQ PLQ
is checked. The required decrease can be set with the hysteresis Hmin. A corresponding
indicator for a full tank is shown in the component symbol.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The ElectricalHeaterGas component type is used for simulation of an electric gas heat
exchanger. The electrical heating power Pel is specified in kW with connector ElectricalPower.
The heated gas is directed via the connectors TS_IN and TS_OUT. The flow P
& is throttled
according to the relationship
ෙS P
& VHF
EDU NJ K
N9 ˮ76
P
with throttle coefficient kV. The reference direction for the flow is chosen as from TS_IN to
TS_OUT.
For the heat transfer, a simple one tube model divided into segments is applied. The number N
of segments can be set to a value between 4 and 16.
PF
& 7 +* +7 3HO
* *
+* +7
... ...
+*1 +71
① Tube side
② Tube
It is assumed that the supplied electrical energy is completely converted into heat. The heat
balance for a segment i of the spare tube with extremely simplified heat transfer is then given
by
G7*L
D7 3HO E7 7*L 77L
GW
with
$˞
D7 E7
07 F7 07 F7
In addition, the heat balance of the gas in a segment i is given by
G7*L
D 7* L 7*L E 77L 7*L
GW
with
1P& $˞
D E
ˮ9 F* ˮ9
TT,i and TG,i are the temperatures of the tube segment and the gas in segment i. The values of
the flow network apply for the density ρ and the specific heat capacity cG of the gas.
Parameters
Additional parameters
Operating window
The following variables are displayed in the operating window:
Symbol
Function
The HeatExchangerGas component type is used to simulate a heat exchanger for the gases on
the tube side and shell side. The simulation is implemented for these three types:
● Parallel-flow heat exchanger
● Counter-flow heat exchanger
● Cross-flow heat exchanger
Both media are routed on the tube side via the connectors TS_IN and TS_OUT, and on the shell
side via the connectors SS_IN and SS_OUT.
The flow P
& is throttled on the tube side and shell side according to the relationship
ෙS P
& VHF
EDU NJ K
N9 ˮ76
P
with the relevant throttle coefficient kv. The chosen reference direction for the flow is from
connector _IN to _OUT on the tube side and shell side.
For the heat transfer, a simple one tube model divided into segments is applied. The number N
of segments can be set to a value between 4 and 16.
① Tube-side space
② Tube
③ Shell-side space
The gas heat on the tube and shell side and the heat in the tube itself are balanced.
7XEHVLGHPHGLXP 776
4& 76LQ 4& 76RXW
4& 776
7XEH 77
4& 667
4& 66LQ 4& 66RXW
6KHOOVLGHPHGLXP 766
The two heat transfers, from the shell side gas to the tube, and from the tube to the tube side
gas are set according to
G776L
D76 776 L 776L E76 77L 776L
GW
G77 L
D7 766 L 77 L E7 776 L 77 L
GW
GK66 L
D66 K66 L K66 L E66 77L 766 L
GW
apply with the following coefficients, which are the same for all segments:
1P & 76 $76 ˞76 1P & 66 $66 ˞66 $66 ˞66 $76 ˞76
D 76 E76 D66 E66 D7 E7
ˮ76976 F76 ˮ76976 ˮ66966 F66 ˮ66966 0 7 F7 07 F7
The values set for the gases in the shell side and tube side of the flownet apply to the densities
pTS, ρSS and the specific heat capacities cTS, cSS.
For initialization, the temperatures of the tube segments are set to the temperature of the tube
side gas, calculated from the specific enthalpy ( FNTS.HSPEC input).
Parameters
Operating window
The following variables are displayed in the operating window:
The CTE component type editor enables you to create your own component types, which utilize
the mechanisms of the FLOWNET process. You can expand the functions of the components
supplied with the FLOWNET library, for example, add physical effects that are not covered by
the supplied library components and thus enhance your flownet simulations. You can also
extend the FLOWNET library by creating your own component types from scratch.
Two aspects must be considered when creating components:
● The topological aspects
● The connection to the solution procedure
The topological aspect is covered by appropriate extensions to the component type definition.
Special connection types are provided for the connection to the solution procedure.
In addition, the general descriptions of component properties in the "SIMIT – Component Type
Editor" manual form the basis for creating flownet components. The general properties also
apply in full to flownet components.
The topology of a flownet is automatically determined when compiling a simulation project from
interconnected flownet components. Each flownet component must thus provide relevant
topological information about itself, which means information about how it is to be treated
topologically in the flownet. From a topological point of view it is necessary to know how the
reference directions for variables in a flownet are defined for a component and how the data
exchange between the component and the solution procedure for the flownet is set up.
The flownet elements with topological information are:
● Internal nodes
● External nodes
● Branch objects
Relationships with the topological connectors of the flownet component must be defined for
each of these elements. To do this, open the topology editor by double-clicking on the Topology
node in the navigation of the component type.
&RQQHFWRUVRIW\SH
)/1
If topological connectors are connected with each other by a connecting line in the chart editor,
then the connected connectors are hidden. They are still visible only as pale shadows.
They can also be joined by superimposing the connectors. Once linked, both connectors are
hidden.
INTERNAL_NODE i;
Topological connectors of the component must also be assigned to this internal node. Three
connectors can be assigned in the topological description as per the example below:
FROM i TO a;
FROM i TO b;
FROM i TO c;
The three connectors a, b and c must be defined as type FLN1 connectors in the component
type. The figure below shows a diagram of the resulting topological structure of the component
type.
EXTERNAL_NODE e;
This external node must be also be linked to at least one topological connector of the
component. The topology description is, for example, to be completed as
FROM e TO a;
. The topological connector a must be defined in the component type as a connector of type
FLN1. The figure below shows a diagram of the resulting topological structure of the component
type.
The reference direction for the variables of a branch object is defined in the topological
description of the flownet component. For example, the definition
FROM a TO b;
defines the branch object with a reference direction from connector a to connector b of the
component. Both of the topological connectors a and b must be defined in the component type
as connectors of type FLN1.
Flow variables are positive in the reference direction. For a branch object, these are the mass
& and the enthalpy flow + PK
flow P & .
Reference direction
Pressure boosts are applied in the reference direction, which means the pressure change is
defined here as
∆p = pb − pa
. For pressure drops in the reference direction (throttling), ∆p is therefore negative and positive
∆p for pressure boosts in the reference direction.
The flownet objects of a component and the flownet solution procedure exchange data via
special flownet connectors. There are six different connector types FLN2 to FLN7 available for
this purpose. Their use in flownet componetns is explained in the sections Connector type
FLN2 for branch objects (Page 777) to Connection type FLN7 for parameter assignment of an
internal node (Page 782).
)ORZQHWFRPSRQHQWV
)ORZQHWVROXWLRQPHWKRG
Connectors of the types FNL2 to FNL7 provide a connection to the flownet solution procedure
and therefore must be set as invisible in the component symbol. In the connector properties, the
usage "Only in property view" or "Only in CTE" must be set.
See also
Connector type FLN6 for parameter assignment of a branch (Page 782)
FROM a TO b : FN;
The connector must always be defined in the OUT direction. It connects the component to the
flownet solution procedure to exchange various variables that are relevant to the branch object
between the flownet solution procedure and the component. It maps the branch-influencing
effect (which means the effect that the branch object has on the branch) to the flownet.
The figure below shows the input and output signals with the direction of data flow between the
component and the flownet solution procedure.
)ORZQHWVROYHU
The component receives four variables for calculating the effect of the branch object via the
input signals:
1. Specific enthalpy h (FN.HSPEC),
2. Mass flow P
& (FN.MFL)
3. Pressure pa (FN.PRESSURE),
4. Density ρ (FN.DENSITY).
The pressure pa relates to the "from" connector (FROM) of the topological description, which is
the connector a in our example. Density ρ and enthalpy h are variables of the supplied medium.
Reference direction
The output signals for the branch object are calculated in the component and sent to the flownet
solution procedure:
1. Change in specific enthalpy Δh (FN.DELTAH),
2. Pressure change Δp = pb − pa (FN.DELTAP)
3. Derivation of the change in pressure based on the mass flow GෙS G0
& (FN.DPDMFL).
EXTERNAL_NODE e : FN;
The connector type FLN3 provides signals in the forward and reverse direction as listed in the
table below.
The following applies: If the FN connector is defined with the direction OUT, then the pressure
and specific enthalpy are specified via this connector for the external node of the flownet. If the
connector is defined with the direction IN, the mass flow rate and the specific enthalpy are
specified for the external node.
At its inputs, the mass flow supplied to or discharged from the flownet via the external node and
calculated by the flownet solution procedure is returned to the components. In the case of
discharge from the flownet, the specific enthalpy of the flow is also returned to the component:
1. Mass flow P
& (FN.MFL)
2. Specific enthalpy ha (FN.HBW)
The figure below illustrates the signal direction for data exchange between the component and
the flownet solution procedure.
)ORZQHWVROYHU
Regardless of the direction selected in the topology description, the mass flow P & is always
positive for inflows to the flownet ( P
& ! ) and negative ( P
& ! ) for outflows.
Reference direction
)ORZQHWVROYHU
Mass flow nodes operate in the flownet like internal nodes with mass inflow or outflow. These
nodes are therefore treated as internal nodes in the flownet, which means an internal node with
additional inflow or outflow is created in the flownet for an external node. The pressure returned
to the component pe therefore corresponds to the pressure in this internal node, and the specific
enthalpy he corresponds to the specific enthalpy of this internal node.
Reference direction
INTERNAL_NODE i : FN;
The connector must always be defined in the IN direction. It connects the component to the
flownet to map the variables that are relevant for the internal node i from the flownet solution
procedure to the component.
The variables calculated in the node i are provided by means of the connector inputs:
1. Pressure pi (FN.PRESSURE)
2. Specific enthalpy hi (FN.HSPEC)
3. Density ρi (FN.DENSITY)
)ORZQHWVROYHU
Note
The relationships used for calculation of the flownet variables, such as temperature, are
defined via the MEDIUM parameter for the relevant medium. This can only be done during
initialization of the simulation. Changes made to the parameters while the simulation is running
have no effect.
Signal Meaning
MEDIUM Flownet medium:
MEDIUM := 0 for water/steam,
MEDIUM := 1 for ideal gas,
MEDIUM := 2 for liquid;
must not be changed while the simulation is running
CG Specific compression modulus K / M for water/steam medium with density ρ < 500 kg/m3 and for ideal
gas medium
CL Specific compression modulus K / M for water/steam medium with density ρ ≥ 500 kg/m3 and for liquid
medium
MG Thermal factor 1 / M for water/steam medium with density ρ < 500 kg/m3 and for ideal gas medium
ML Thermal factor 1 / M for water/steam medium with density ρ ≥ 500 kg/m3 and for liquid medium
P_INIT Initial value for the pressure in the internal nodes of the flownet
H_INIT Initial value for the specific enthalpy in the internal nodes of the flownet
DENSITY Density of the medium in the flownet when liquid is set as the medium
T_ENV Ambient temperature
C_ENV Heat transfer factor c = αA for heat exchange in the internal nodes of the flownet with the environment
L_CR Specific heat capacity cp for liquids as medium
IG_R Specific gas constant RS for ideal gas as medium
IG_CR Specific heat capacity cp for ideal gas as medium
ST Binary signal; if ST := "True", then a linear transfer is applied for parameters CL, CG and ML, MG for
the water/steam medium
AL Momentum factor A for branches in the flownet
Depending on the direction of the connector FN its signals are inputs or outputs. Depending on
the direction, flownet parameters can be set or used in component. If the connector is defined
with direction OUT, the variables set in the component are provided to the flownet as
parameters. These parameters are available in the component for evaluation, if the connector
is defined with direction IN.
FROM a TO b: FN;
If a connector of type FLN6 is defined with direction OUT, then the momentum factor A for the
branch containing the object is transferred to the flownet solution procedure via this connector.
If the connector is defined with direction IN, then the momentum factor A for the branch is
transferred to the branch object by the flownet solution procedure.
Internal_Node i: FN;
The variables listed in the table below are transferred to the flownet solution procedure for the
internal node. You can find their meaning in the mathematical model of the flownet in the
following section: Parameter assignment of flownets (Page 597).
Signal Meaning
CG Specific compression modulus Ki / Mi for water/steam medium with density ρ < 500 kg/m3 and for ideal
gas medium
CL Specific compression module Ki / Mi for water/steam medium with density ρ ≥ 500 kg/m3 and for liquid
medium
MG Thermal factor 1 / Mi for water/steam medium with density ρ < 500 kg/m3 and for ideal gas medium
ML Thermal factor 1 / Mi for water/steam medium with density ρ ≥ 500 kg/m3 and for liquid medium
Signal Meaning
P_INIT Initial pressure value
H_INIT Initial value for specific enthalpy
T_ENV Ambient temperature
C_ENV Heat transfer factor ci = αA for heat exchange with the environment
L_CR Specific heat capacity cp for liquids as medium
IG_R Specific gas constant RS for ideal gas as medium
IG_CR Specific heat capacity cp for ideal gas as medium
You can use various constants and functions when creating your own flownet components.
Constants
The available constants are listed in the table below.
Functions
Functions for calculating state variables are available for flownet components with water/steam
medium. The available state variables and units are summarized in the table below.
Variable Unit
p Pressure bar
pS Saturated steam pressure bar
T Temperature °C
TS Saturated steam temperature °C
h Specific enthalpy kJ/kg
h' Specific enthalpy of saturated water kJ/kg
h" Specific enthalpy of saturated steam kJ/kg
ρ Density kg/m3
ρ' Density of saturated water kg/m3
ρ" Density of saturated steam kg/m3
All state functions FNAME return a state variable ZVAL as an analog value. Calls are performed
as follows:
ZVAL = _WaterSteam.FNAME(PARAM1 (, PARAM2)).
The saturated steam pressure pS and saturated steam temperature TS are limited for the
saturation functions as follows:
0 ≤ TS ≤ 373.94 °C and 0.0065 bar ≤ pS ≤ 220.64 bar.
The relevant limit is set for values outside this range.
The values for pressure p and specific enthalpy h are limited to the following ranges for the state
function ρ = ρ(p,h):
0.007 bar ≤ p ≤ 490 bar and 20 kJ/kg ≤ h ≤ 3998 kJ/kg
For the state function T = T(ρ,h), the specific enthalpy is limited to the range
9 kJ/kg ≤ h ≤ 4158
kJ/kg. The limits for the density ρ depend on the enthalpy value: The lowest valid density value
is 0.0012344 kg/m3 (with h = 4160 kJ/kg); the highest valid density is 1045.239 kg/m3 (with h =
96 kJ/kg).
The auxiliary function Cylniv can be used to calculate fill levels in horizontal cylinders. For a
cylinder of length L and radius r with specified volume V, it calculates a fill level of H. Its call is:
H = _Utilities.Cylniv(V, L, r).
User-defined functions
The FLOWNET library provides you with three different media: water/steam, ideal gas and
liquid. The medium to be used is set in the signal MEDIUM of the connection type FLN5 with a
corresponding ID (0, 1, or 2). You can find additional information on this in section: Connector
type FLN5 for parameters of a flownet (Page 781).
The state equations for density and temperature that are defined for the relevant medium are
accordingly applied by the flownet solution procedure.
With the FLOWNET library you also have the option of performing flownet simulations with
other media besides the pre-defined media. You have to provide the media-specific state
equations for the calculation of density and temperature in the nodes by means of a “global
function”.
Such a global function must consist of a .NET assembly that is named Userdefined.dll and
which has its "Assembly Name" specified as "Userdefined" in the project settings. It must have
the namespace Userdefined and a public class named FlownetFunctions. This class must
contain two public static functions for calculation of the state variables:
● public static double trh(long m, double r, double h)
● public static double rph(long m, double p, double h)
The function trh has to calculate the temperature from the density r and the specific enthalpy h;
the function rph has to calculate the density from the pressure p and the specific enthalpy h. The
units of the variables are to be assumed as follows:
● Temperature in °C,
● Density in kg/m3
● Pressure in bar, and
● Specific enthalpy in kJ/kg.
The medium has to be specified by a freely selected negative number. This negative media key
number forms the first transfer parameter m of both functions. In your own functions you only
need to consider the user-defined negative media key numbers; if the value given is ≥ 0
computation will be performed by SIMIT, and your functions will not be called in this case.
This means you have the option of defining any desired media in these two functions and of
using them in a simulation project. Note that in your user-defined functions, you only need to
pay attention to negative media key numbers. For non-negative media key numbers, the
functions that are included in SIMIT are used. Your user-defined functions are not called by
SIMIT in this case.
The scope for your user-defined functions might be set up as follows:
namespace Userdefined
{
public class FlownetFunctions
{
public static double trh(long m, double r, double h)
{
switch (m)
{
case -1:
// Calculation for media with key number -1 …
return 0.0;
case -2:
// Calculation for media with key number -2 …
return 0.0;
default:
// Should not occur!
return 0.0;
}
}
To assign a specific medium to a flownet, set the relevant media key number in the MEDIUM
signal of the FLN5 connector type; in the case of user-defined media this means setting the
relevant negative value.
Note
If you set a negative key number for the medium without providing the necessary functions for
the calculation of density and temperature, the flownet solution procedure assumes that the
density and temperature are zero.
Note
Modifications to the assembly do not affect existing simulation projects. The modified assembly
affects newly-created projects. If you want to use the modified assembly in projects that already
exist, copy it into the globalFunctions folder in these projects.
,QLWLDOL]LQJIORZQHWFRPSRQHQWV
,QSXWV 2XWSXWV
'HIDXOWV ,QLWLDOL]DWLRQV
,QLWLDOL]DWLRQYDOXHVRIWKHIORZQHWVROXWLRQ
PHWKRG
Since no variables of the flow network solution are available for component initialization, it is
advisable to preassign suitable values to the component type inputs. We recommend values
that are consistent with the default values of the flownet solution procedure.
8.3.1 Introduction
The CONTEC library is an extension of SIMIT, which provides component types for creating
simulations of conveyor systems. By linking components of this library, you can create a model
of a conveyor system in SIMIT to simulate the transport of objects in this system. The CONTEC
library provides a special solution procedure for this purpose for use in SIMIT. Once the
simulation has started, the solution procedure continuously calculates the positions of the
objects in the modeled conveyor system.
The CONTEC library is only suitable for simulating conveyor systems for individual objects;
bulk material conveyor systems cannot be simulated. In addition, the simulation is limited to
conveyor systems in which the transportation routes for the objects are fixed by the
arrangement of the handling equipment. Conveyor systems with autonomously operating
vehicles, which means vehicles that determine their own transportation route, are therefore
excluded.
SIMIT provides a real-time simulation for the virtual commissioning of user programs for
automation systems. Likewise, the simulation of conveyor systems with the CONTEC library is
always used in a closed circuit with real or simulated automation systems. This sort of
simulation with SIMIT is therefore fundamentally different from the material flow simulations
used for planning and designing conveyor systems. There, the material flow in a conveyor
system is simulated on the basis of a pre-defined control strategy, whereas here the control
strategy is translated into an actual automation system, which includes a simulation of the
purely mechanical elements of the conveyor system created with SIMIT. To differentiate it, this
type of simulation is therefore referred to as material handling simulation in this manual.
As is usual in SIMIT, material handling simulations are easy to create with the CONTEC library,
using components from the graphical user interface. The emphasis in implementing the
component types in the library was on the simple creation and parameter assignment of the
simulation model and on the stability of the model in the simulation, rather than on a detailed
simulation of the mechanical aspects of conveyor systems. Material handling simulation is
therefore based on a movement model that simulates the movement of objects along paths at
a pre-defined speed, the paths being determined by the handling equipment. The weight of the
object and other factors influencing movement, such as friction, for example, are disregarded.
Two types of conveyor systems can be simulated with the component types provided in the
CONTEC library:
● Conveyor systems with rail-mounted vehicles
such as electrical overhead monorails, ground transport systems, etc. and
● Non-vehicular conveyor systems
such as chain, roller and belt conveyor systems, etc.
Component types are also available in CONTEC that allow you to include RFID, Moby, bar
code, etc. in the simulation.
You can use SIMIT to create your own library components for material handling simulations and
thus expand your material handling library. You can use the special CONTEC solution
procedure for material handling simulation in the component types by means of special
connection types.
Note
If there are material handling components in your simulation project, which means components
that use the material handling solution procedure, then the simulation can only be run if you
have a material handling license.
Material handling describes the technology used for moving objects in any direction over limited
distances. Objects can generally be moved in any spatial direction. Handling equipment refers
to the individual machines that are used to move the object in the conveyor system.
The CONTEC material handling library can be used to create simulation models of a conveyor
system and to run simulations with them. The handling equipment is subject to the following
restrictions:
● All transportation routes are defined as linear paths.
● Transportation routes and possible branches must be predefined as a structure of the
conveyor system for a simulation.
This section is clearly an open conveyor system network with the three boundary points R1, R2
and R3. If the object crosses the boundary of a conveyor system network it is lost, which means
it is removed from the handling equipment and returned to the material list where it is once more
available for use. Components can remove objects from or feed them into the conveyor system
network at the boundaries by means of suitable connections to the solution procedure.
The special solution procedure of the material handling calculates the position of the objects at
equidistant times, as is usual in SIMIT. It supplements the standard SIMIT solution procedure
so that material handling component types can be used alongside other component types, for
example, component types from the basic library. To enable data to be exchanged, material
handling components are connected to the material handling solution procedure by means of
specific connections. They receive values calculated by the solution procedure and send
variables to the solution procedure via these connections.
For each segment in the conveyor system network, positions can be defined at which sensors
detect the object as it passes. The material handling solution procedure then ensures that the
relevant sensor signals are activated in the simulation according to the positions and
dimensions of the objects.
Here you can define which object components are available in the simulation. For each
component type you can specify the number of instances to be formed. To create an instance,
simply drag the component type you want from the MATERIAL directory of the CONTEC library
into the editor. To create more than one instance, hold down the Alt key as you drag the
component type. A query dialog will appear in which you can specify the number of instances,
as shown in the figure below:
You can also create several material lists in the "Lists" project folder and sort the material lists
into different folders if necessary.
In order to place object components on a specific section of the simulated transport network for
the start of the simulation, you can assign one or more object components of the same type
from the material lists in the project to the component simulating the section.
You can find examples for this in the following sections:
● Rail-S4 – Straight rail with four sensors (Page 808)
● Conveyor-S4 – Straight conveyor with four sensors (Page 824)
If object components have a behavior model (behavior description), this is executed at the start
of the simulation in the same way as it would be if the object components were placed on a chart
like other components. The simulation of the behavior of an object defined by that description
is entirely independent of the treatment of that object in the solution procedure for the material
handling simulation.
Once the simulation has started, each object defined in the material list is given a unique
identification number which is automatically set by SIMIT and displayed in the material lists.
If an object is detected at a sensor during the simulation, the solution procedure returns the ID
of the detected object component.
Modeling segments
A segment is modeled as a line. It is defined by its two end points, the geometry and the
direction of the segment. The geometry can take the form of a straight line or an arc. It is defined
by the position of its two end points A and B and its angle. If the angle is not zero, there are two
possible segments which can be differentiated by the sign of the angle: a positive angle means
that the center point of the arc is located to the right of the segment in the counting direction,
while a negative angle means that the center point of the arc is located to the left of the segment.
The radius of the arc is determined by these three variables. The direction of the segment
corresponds to the reference direction for transporting the objects.
The object being transported over a segment is rotated by the angle of the segment. This
means on straight segments the object is transported without being rotated; the absolute
orientation of the object is maintained. The figure below shows the transport of an object over
a straight and a curved segment:
For each segment a speed is defined at which the objects are transported over that segment.
Positive speed values cause the object to be transported in the reference direction, while
negative speed values cause it to be transported against the reference direction. The inherent
speed of an object is added to the segment speed where applicable.
A state is assigned to each segment for movement in the reference direction and for movement
against the reference direction. This state identifies a segment as "active" or "inactive" in the
corresponding direction. Inactive segments are regarded as non-existent in the material
handling solution procedure. This means that objects cannot be moved on these segments,
and the positions of objects already located on these segments are not updated. In addition,
sensors on inactive segments are not updated. The change in state of segments is used to
specify an explicit transportation route at branches. The figure below shows an example of how
a switch function can be modeled by alternately activating and deactivating the two segments
in the reference direction:
Positions at which the transport of an object can be blocked can be defined on a segment. The
state of a stopper position can be set to "active" or "inactive". If a stopper is active, all objects
are stopped at this position and all downstream objects are held up accordingly as shown in the
figure below by way of example:
6WRSSHUV
'LUHFWLRQRIPRWLRQ
In addition, positions at which an object can be detected can be defined on a segment as sensor
positions. At each of these sensor positions the identifier (ID) of the object covering the position
is then recorded in the material handling solution procedure. The detection range for the objects
can also be defined for each sensor position. This range is defined as a percentage of the object
size and is assumed to be symmetrical with respect to the center of the object. The figure below
illustrates the detection of an object for two different detection ranges: the top row shows the
activation of a sensor for the full detection range (100%) of the object; the bottom row shows the
activation of a sensor for half the detection range (50%). The detection range for the object is
shown in gray in each case and movement is assumed to be from left to right.
6HQVRU
'LUHFWLRQRIPRWLRQ
Component types in which only one segment with sensors is modeled include, for example, the
straight rail (Rail-S4) and the straight conveyor (Conveyor-S4).
Modeling branches
Because all sections are assumed to be linear, a branch is a point in the conveyor system
network at which more than two segments connect.
In the subnetwork of a component type a branch can either be shown as a connector, which
means a shared end point of multiple segments (as shown in figure below on the left), or it can
be located within a subnetwork (as shown in figure below on the right). In the first case the
position of the branch point is given directly by the position of the connector, whereas in the
second case the branching position is defined relative to the component.
At branch points the transportation route must be explicitly defined at every moment of the
simulation. In other words, no more than two of the segments that connect at a branch may be
active as a transportation route at any given time. Therefore activation of the segments must be
included as a function in the component type.
Modeling boundaries
Boundaries are end points of a segment that are not connected to other segments. For a
component like a straight conveyor, for example, a boundary of the conveyor system network
is created if a connector of this component is not connected to other components. In the
simulation, if an object moves beyond such a boundary point it is removed from the conveyor
section and returned to the material list. A message to that effect appears in the message line.
%RXQGDU\
SRLQW
Boundary points can also be defined as end points in the subnetwork of component types. The
behavior of an object passing this boundary point can then be freely defined in the component
type using suitable functions. For example, the position of the object can be freely calculated
to simulate complex movements. You can find examples for such components in the following
sections:
● Turntable-R60 – Turntable (Page 846)
● TransferCarriage – Transfer carriage (Page 851)
Objects with other rotation angles ϕ are also held up. However, as their position can only be
calculated approximately, this leads to overlaps.
a
The effective width E of an object that is used as a simplification to simulate the holdup is
calculated using the following formula:
a ˳K ˭ ˳ E
E
˭
where h denotes the height and b the width of the object.
Holdup in trends
Modeling of the holdup behavior has been simplified to a great extent. This means the positions
of held-up objects in the simulation do not necessarily correspond to the actual positions in all
cases.
In trends, too, the position of held-up objects is only an approximation. The held-up objects
overlap, as shown in the figure below.
The overlaps are caused by the fact that the bend of the trend is disregarded in the distance
calculation.
8.3.2.5 Scalability
Unlike in the standard library, the dimensions of components play a decisive role in the
conveyor technology library because they directly indicate the length of conveyor sections or
the dimensions of objects. In accordance with standard engineering practice, millimeters [mm]
are used throughout as the length unit, while speeds are given in meters per second [m/s].
Note
If you have licensed the material transport library for your SIMIT installation, the sizes of all
components, including components from the basic library, are reproduced at the specified
scale. For basic library components you can retain the intended sizes by choosing a scale of 1
pix : 1 mm for charts containing basic components.
To avoid having to set the scale individually for each chart, you can choose a default setting for
the entire project in the property view of the Project Manager.
This scale is used as the default for all new charts that you create.
Note
Setting a default scale in the Project manager does not change the scale of any existing charts.
Note that changing the scale of a chart does not change the displayed size of a component, but
rather its effective dimensions in millimeters.
Scalability of objects
Objects are shown in the material lists of a SIMIT project with their absolute size (width and
height) in millimeters. This means objects are represented on charts in differing sizes,
depending on the chosen scale of the chart.
The dimensions of an object are pre-defined in the component type. So when you add an object
to the material list, it is added with the width, height and depth defined by the component type.
You can then change the dimensions for each object in the material list, provided that the
component is scalable. The object types provided in the CONTEC library are all scalable.
Note
Note that width and height refer to the dimensions of the object as viewed from above, as shown
in the diagram. The depth is the size in the third dimension, which is not shown. This definition
was chosen so as to retain the meaning of the height and width of components and graphics on
a chart. The component types provided in the material handling library disregard the depth of
the object. With the component types available in the library, objects of any depth are detected
by sensors solely on the basis of their width and height. For that reason the depth of objects is
set to zero by default. The depth of objects only becomes important if you create a custom
material handling component type that evaluates the depth of an object, for example a height
check, and use it in your material handling simulation.
You can find additional information on this in the section: Creating custom component types for
material handling simulation (Page 892).
If you want to set the dimensions of several objects to the same value, you can copy the value
for one object, in other words from one row of this table to any number of others. Follow the
steps outlined below:
● Select the row containing the required object value.
● Right-click on the cell containing the value to be copied and select "Copy Cell" in the shortcut
menu.
As conveyor sections can be shown to scale on charts as a system layout using appropriate
components, there is no point in also showing all additional input and output signals for these
components in graphical form in these charts. This would compromise the clarity of the system
layout. This means the only visible connectors on the component types in the CONTEC library
are those used to connect them to each other to construct the system layout. Connectors for
connecting components to the associated drive and sensor signals, and hence via the
couplings to the controller signals, are implemented by means of an implicit assignment of the
inputs. You have various options for connecting components. They are explained below by
reference to a simple rail.
This means its Speed input is predefined so that it is implicitly connected to output Y of the
component with the name Rail-Speed.
You can therefore create a chart which in this example contains a component with the name
Rail-Speed and has an output Y which then defines the percentage speed for this rail.
Alternatively, you can also enter every other (analog) output of a component in the Speed input
for the rail by changing the setting from to and entering the corresponding output signal, as
shown by way of example in the figure below.
If you want the speed defined by the rail to be constant, you can also set the Speed input to
and enter the desired percentage directly.
If you want to be able to further process output signals for the rail sensors, you would likewise
use implicit connections. You can use any components and assign their (binary) inputs
accordingly, as shown by way of example in the figure below.
Using templates
Templates can be used as a way of creating charts for drive and sensor simulation with minimal
effort.
The material handling library includes suitable templates for connecting the drive and sensor
signals for every component type of a conveyor section, as well as for the vehicles. The
template names are the same as the names of the component types.
All templates include a component from the basic SIMIT library for simulating the drive. In
addition, the template can also be used to connect the simulated sensors in the conveyor
section to the controller via coupling signals. The template for the "Rail-S4" component type is
shown in the figure below.
If you use an identification system that allows the symbolic names of the I/O addresses to be
derived from the names of the conveyor sections, you can modify these templates accordingly.
You can then obtain the full connection of the corresponding conveyor section to the controller
via the coupling by instantiating the template.
To connect all conveyor sections in the simulation project to the controller with the minimum
possible effort, use the "Instantiate templates" function.
Note
You have to adapt the names of the input/output signals in the templates to your identification
system to gain the maximum benefit from this method.
Using the Topology connector, a topological connection can be created between two or more
material handling components. Under (b) in the figure below, two components are connected
by the CON_A connector. The connection is functionally identical to the direct connection of
both components via a connecting line, as shown under (a) in the figure below.
The figure below shows three components connected by the CON_A connector. This
configuration is not valid, because with material handling components only two topological
connectors can ever be connected to one another.
If you start a simulation project containing a configuration like this, an error message will appear
as shown in the figure below and the simulation is aborted.
The RAILS directory of the CONTEC library contains component types for use in vehicular
conveyor system simulations. In the broadest sense these types simulate "rails" on which
vehicles can be placed as objects. The vehicles are either moved at the speed set by the
individual rail segment or the vehicles set the speed themselves. A superposition of both
speeds is also possible, although this is not used in practice.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The width of the symbol is scalable. The width corresponds to the length of the rail
section.
Function
The Rail-S4 component type is used for simulating a straight rail section. The speed at which
vehicles are moved over this rail section is set at the hidden Speed input of the component as
a percentage of the configurable nominal conveyor speed (NominalSpeed parameter).
Between one and four sensors can be positioned along the length of the rail. When a vehicle
is within the detection range of a sensor, the corresponding hidden binary output Sensor1 to
Sensor4 is set. The ID of the detected vehicle can be obtained via the corresponding hidden
integer outputs SensorId1 to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NbrOfSensors
Number of sensors used (1 to 4)
● SensorPosition
Position of the corresponding sensor relative to connector A of the symbol.
When the simulation is running, every defined sensor is shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
The validity of the parameters is checked while the component is being initialized. The following
messages indicate possible parameter assignment errors:
● Parameter 'SensorPosition' must be less than the component's width
The sensor position must not be outside the component.
● Parameter 'SensorPosition' must not be negative
The sensor position must not be negative.
Additional parameters
The Rail-S4 component includes the additional parameters TEMPLATE and HIERARCHY,
which can be used to control generation of the drive level. You can find additional information
on this in section: Using templates (Page 803).
Further additional parameters can be used during initialization to place vehicles on the rail.
● MaterialType
The type of vehicle that is to be placed
● MaterialList
The name of the material list from which the vehicle is to be taken. If this parameter is left
blank, all the material lists in the simulation project are searched.
● InitNbrOfObjects
The initial number of vehicles to be placed on the rail
● Clearance
The distance between the vehicles that are initially placed
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of a maximum of four
sensors.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The size of the symbol can be scaled proportionally. The size corresponds to the size
of the rail section. Proportional scaling alters the radius of the curve; the angle of 45° does not
change.
Function
The CurvedRail45-S4 component type is used to simulate a curved rail with a 45° bend. The
speed at which vehicles are moved over this rail section is set at the hidden Speed input of the
component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter).
Between one and four sensors can be positioned along the length of the rail. When a vehicle
is within the detection range of a sensor, the corresponding hidden binary output Sensor1 to
Sensor4 is set. The ID of the vehicles can be obtained via the hidden integer outputs SensorId1
to SensorId4.
Parameters
The behavior of the component can be set by means of a parameter:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NbrOfSensors
Number of sensors used (1 to 4)
● SensorPosition
Position of the corresponding sensor relative to connector A of the symbol.
When the simulation is running, every defined sensor is shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
The validity of the parameters is checked while the component is being initialized. The following
messages indicate possible parameter assignment errors:
● Parameter 'SensorPosition' must be less than the component's length
The sensor position must not be outside the component.
● Parameter 'SensorPosition' must not be negative
The sensor position must not be negative.
Additional parameters
The CurvedRail45-S4 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of a maximum of four
sensors.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The size of the symbol can be scaled proportionally. The size corresponds to the size
of the rail section. Proportional scaling alters the radius of the curve; the angle of 90° does not
change.
Function
The CurvedRail90-S4 component type is used to simulate a curved rail with a 90° bend. The
speed at which vehicles are moved over this rail section is set at the hidden Speed input of the
component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter).
Between one and four sensors can be positioned along the length of the rail. When a vehicle
is within the detection range of a sensor, the corresponding hidden binary output Sensor1 to
Sensor4 is set. The ID of the vehicles can be obtained via the hidden integer outputs SensorId1
to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● MaxSpeed
Nominal conveyor speed; adjustable online
● NbrOfSensors
Number of sensors used (1 to 4)
● SensorPosition
Position of the corresponding sensor relative to connector A of the symbol.
When the simulation is running, every defined sensor is shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
The validity of the parameters is checked while the component is being initialized. The following
messages indicate possible parameter assignment errors:
● Parameter 'SensorPosition' must be less than the component's length
The sensor position must not be outside the component.
● Parameter 'SensorPosition' must not be negative
The sensor position must not be negative.
Additional parameters
The CurvedRail90-S4 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of a maximum of four
sensors.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The size of the symbol can be scaled proportionally to adjust the size of the switch.
Proportional scaling alters the length of the switch and the radius of the spur curve, but the spur
angle of 45° does not change.
Function
The RailSwitch-F component type is used to simulate a branch (switch) or junction with a 45°
spur. It functions as a switch when objects are moved in the reference direction and as a
junction when they are moved against the reference direction.
If the hidden binary input Switch is set to one (True), transport is switched from the straight
section (A – B) to the spur (A – C). Note that transport against the reference direction is likewise
only possible over an active segment.
The speed at which vehicles are moved over the rails is set at the hidden Speed input of the
component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter).
The switch cannot be operated if it is occupied by vehicles. If an attempt is made to operate an
occupied switch, the following error message appears: "Switch cannot be operated while being
occupied".
Parameters
The behavior of the component can be set by means of a parameter:
● NominalSpeed
Nominal conveyor speed; adjustable online
The parameter, its unit and default value are shown in the figure below.
Additional parameters
The RailSwitch-F component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and switch the sections.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The size of the symbol can be scaled proportionally to adjust the size of the switch.
Proportional scaling alters the length of the switch and the radius of the spur curve, but the spur
angle of 45° does not change.
Function
The RailSwitch-M component type is used to simulate a branch (switch) or junction with a 45°
spur. It functions as a switch when objects are moved in the reference direction and as a
junction when they are moved against the reference direction.
The hidden analog input Switch is used to move the switch from transport over the straight
section (A – B) to transport over the spur (A – C). The switching time is configurable
(SwitchingTime parameter). Positive values at the Switch input move the switch to the A – C
section, while negative values move it to the A – B section. The absolute values are
percentages of the configurable switching speed. The moving operation for a component is
shown in animated form in the symbol.
The speed at which vehicles are moved over the rails is set at the hidden analog input Speed of
the component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter).
The switch cannot be moved if it is occupied by vehicles. If an attempt is made to move an
occupied switch, the following error message appears: "Switch cannot be operated while being
occupied".
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● SwitchingTime
Switching time for the switch when triggered with +/- 100% values at the Switch input.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The RailSwitch-M component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can use a slider to set the conveyor speed as a percentage of the
nominal conveyor speed (NominalSpeed) and the switching time as a percentage of the
configurable switching time (SwitchingTime).
Symbol
The width of the symbol is scalable. The set width corresponds to the length of the inward/
outward section.
Function
The InOut component type represents a section over which vehicles are moved into or out of
a conveyor system network. The InOut component is connected to an open section of the
network at connector A to extend the conveyor system network.
To move them into the network, individual vehicles are placed on the unconnected end of the
inward/outward section (left edge of the symbol) by setting the hidden binary input
CreateObject and moved from there to connector A. Correspondingly, vehicles to be moved out
of the network are moved from connector A to the unconnected end of the inward/outward
section, from where they are removed from the conveyor system network. The speed at which
vehicles are moved over the inward/outward section is set at the hidden Speed input of the
component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter).
The inward/outward section can only be occupied by one vehicle at a time. If the section is
occupied by a vehicle, no other vehicle can be positioned to be moved into the network or
removed from the network.
Parameters
The type of vehicles to be moved into the network, the material list from which they are taken
and the speed at which the vehicles are moved over the inward/outward section can be set by
means of parameters.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The InOut component includes the additional parameters TEMPLATE and HIERARCHY,
which can be used to control generation of the drive level. You can find additional information
on this in the section: Using templates (Page 803).
Operating window
In the operating window, you can place a new vehicle on the inward/outward section by clicking
the pushbutton.
RailLifter – Lifter
A lifter is a rail that can be moved vertically through several levels. In SIMIT a lifter is made up
of the base component of the RailLifterBase type and up to eight expansion components of
the RailLifterExtension type. The base component simulates the lifter in the base level, while
each additional level is simulated by an expansion component. A lifter that can be moved
through up to eight additional levels can be simulated in this way.
You do not have to position the base component and the associated expansion components on
the same chart. You can create a separate chart for each level, for example, and distribute the
lifter components over the individual charts.
The following points apply to the parameter assignment of the base component:
● There are no restrictions on the name of the base component.
● The NbrOfExtensions parameter indicates the number of additional levels and hence also
the number of expansion components used.
● In the base component you have to specify the position (LevelPosition) for each level, which
means the level above the base level in millimeters. The base level is by definition at level
zero. All level values must be positive and increase with the level number.
The following points should be borne in mind when assigning the parameters for the expansion
components:
● The name of the expansion component is formed from the name of the base component, the
'#' character, and a number indicating the level.
● The Level parameter must correspond to the level number. The numbering of the levels
starts with one.
● The BaseName parameter is the name of the base component.
● The length of the lifter is determined by the width of the base component.
Note
All expansion components must be exactly the same width as the base component. Otherwise,
a message will be displayed pointing to this inconsistency when the simulation is started.
The rail drive and the lifter sensors are fully implemented in the base component. This means
expansion components do not work without the base component.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The width of the symbol is scalable. The set width corresponds to the length of the
lifter rail.
Function
The RailLifterBase component type is used to simulate the base station of a lifter. The speed
at which vehicles are moved over the lifter rail is set at the hidden analog input Speed of the
component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter). Similarly, the lifting speed, which means the speed at which the rail is moved to the
different levels, is set at the hidden analog input LifterSpeed as a percentage of the
configurable nominal lifting speed (NominalLifterSpeed parameter).
To move vehicles in and out at the various lifter levels, the lifter rail must be moved to the
appropriate level and stop flush with that level. Flushness must be set with a positioning
accuracy Δ that is the same for all levels (PositioningAccuracy parameter). The rail stops flush
with a level H if the following applies for its level h:
H−Δ≤h≤H+Δ
Between one and four sensors can be positioned on the rail relative to each of the two
connectors A and B. When a vehicle is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected vehicle
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Note
The base component has further hidden inputs for exchanging signals with extension
components. The corresponding signals are assigned to these inputs by default. Do not change
these default settings, otherwise the lifter components will not behave in the intended way in the
simulation.
Parameters
The behavior of the component is configurable.
● NominalSpeed
Nominal conveyor speed; adjustable online
● NominalLifterSpeed
Nominal lifting speed; adjustable online
● NbrOfExtensions
Number of additional levels (1 to 8)
● LevelPosition
Level of the corresponding additional level
● PositioningAccuracy
Positioning accuracy within which the level is deemed to have been reached.
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol
When the simulation is running, the defined sensors are shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The RailLifterBase component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
You also need to specify how many vehicles can be present on this conveyor section at any one
time.
Operating window
In the operating window, you can use a slider to set the transport speed as a percentage of the
nominal conveyor speed (NominalSpeed) and you can monitor the status of the sensors.
In the extended operating window you can move the lifter up or down by means of pushbuttons.
The current lifter position and level are displayed.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
vehicles. The width of the symbol is scalable. The set width corresponds to the length of the
lifter rail.
Note
The width of the extension component must be the same as the width of the base component.
Function
The RailLifterExtension component type is used to simulate a lifter at one of the accessible
levels. A component of this type can only be used in combination with a component of
the RailLifterBase type.
Parameters
The behavior of the component is configurable:
● Level
Level at which the component is located. The numbering starts at one.
● BaseName
Name of the corresponding base component
The parameters, their units and default values are shown in the figure below.
Additional parameters
Specify how many objects can be present on the section (lifter rail) defined by the component
at any one time. This parameter should be set to the same value as for the base component.
Operating window
In the operating window, you can monitor the status of the sensors.
The CONVEYOR directory of the CONTEC library contains component types for use in
simulating conveyor systems such as roller, chain and belt conveyor systems. All of these
components determine the speed at which the object is moved. The object is passive in respect
of these components, in other words it generally does not have its own drive. These
components are typically used to transport pallets, containers or capital goods.
All component types of the CONVEYOR library have a fixed symbol height of 40 pixels.
According to the selected scale the width of the conveyors can be adjusted to the values listed
in the table below.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
No transport
The width of the symbol is scalable. The set width corresponds to the length of the conveyor.
Function
The Conveyor-S4 component type simulates a straight conveyor section of a given length. The
speed at which objects are moved over this conveyor is set at the hidden analog input Speed of
the component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter).
Between one and four sensors can be positioned on the conveyor relative to each of the two
connectors A and B. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol
When the simulation is running, the defined sensors are shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The Conveyor-S4 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Further additional parameters can be used to place objects on the conveyor for the simulation.
These are placed on the conveyor after the start of the simulation, starting at end A:
● MaterialType
The type of object initially placed on the conveyor
● MaterialList
The name of the material list from which the object is to be taken. If this parameter is left
blank, all the material lists in the simulation project are searched.
● InitNbrOfObjects
The number of objects that are to be placed
● Clearance
The distance between the objects that are to be placed
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of the maximum eight
sensors.
In the extended operating window you can remove objects that are currently detected by one
of the eight sensors from the conveyor section (Remove). In addition, you can place new
objects on the conveyor section using the Create pushbutton (Create). The object with the
specified object ID (Object-ID) is then placed on the conveyor at the specified distance (Offset)
from connector A. If no object ID is specified, the system searches the material lists
(MaterialList additional parameter) for an object of the type specified by the MaterialType
additional parameter.
This simulates manual interventions in the conveyor system such as the removal and
placement of objects.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
No transport
The width of the symbol is scalable. The set width corresponds to the length of the conveyor.
Function
The Conveyor-S4-Stopper component type simulates a straight conveyor section of a given
length with a stopper at a given position on the conveyor section. The speed at which objects
are moved over this conveyor is set at the hidden analog input Speed of the component as a
percentage of the configurable nominal conveyor speed (NominalSpeed parameter).
Between one and four sensors can be positioned on the conveyor relative to each of the two
connectors A and B. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
The stopper can be activated and deactivated to stop objects at the stopper position in both
conveyor directions. When a stopper is activated, its color in the symbol changes to red.
Deactivated stopper
Activated stopper
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● StopperPosition
Position of the stopper relative to connector A
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol.
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol.
When the simulation is running, the defined sensors are shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The Conveyor-S4 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Further additional parameters can be used to place objects on the conveyor for the simulation.
These are placed on the conveyor after the start of the simulation, starting at end A:
● MaterialType
The type of object initially placed on the conveyor
● MaterialList
The name of the material list from which the object is to be taken. If this parameter is left
blank, all the material lists in the simulation project are searched.
● InitNbrOfObjects
The number of objects that are to be placed
● Clearance
The distance between the objects that are to be placed:
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of the maximum eight
sensors. The stopper can be activated and deactivated by means of a switch.
In the extended operating window you can remove objects that are currently detected by one
of the eight sensors from the conveyor section (Remove). In addition, you can place new
objects on the conveyor section using the Create pushbutton (Create). The object with the
specified object ID (Object-ID) is then placed on the conveyor at the specified distance (Offset)
from connector A. If no object ID is specified, the system searches the material lists
(MaterialList additional parameter) for an object of the type specified by the MaterialType
additional parameter.
This simulates manual interventions in the conveyor system such as the removal and
placement of objects.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
Function
The ConveyorCurve45-R60 component type is used to simulate a curved conveyor. The
conveyor section forms a 45° arc. The component symbol cannot be scaled. The radius of the
arc is set to 60 pixels and cannot be changed. The effective radius of the component is
determined by the scale set for the chart. For example, a scale of 1 pix: 100 mm gives an
effective radius of 6 meters.
The speed at which objects are moved over this conveyor is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter).
Parameter
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The ConveyorCurve45-R60 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
Function
The ConveyorCurve45-R100 component type is used to simulate a curved conveyor. The
conveyor section forms a 45° arc. The component symbol cannot be scaled. The radius of the
arc is set to 100 pixels and cannot be changed. The effective radius of the component is
determined by the scale set for the chart. For example, a scale of 1 pix: 100 mm gives an
effective radius of 10 meters.
The speed at which objects are moved over this conveyor is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter).
Parameters
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The ConveyorCurve45-R100 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
Function
The ConveyorCurve45-R200 component type is used to simulate a curved conveyor. The
conveyor section forms a 45° arc. The component symbol cannot be scaled. The radius of the
arc is set to 200 pixels and cannot be changed. The effective radius of the component is
determined by the scale set for the chart. For example, a scale of 1 pix: 100 mm gives an
effective radius of 20 meters.
The speed at which objects are moved over this conveyor is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter).
Parameters
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The ConveyorCurve45-R200 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
Function
The ConveyorCurve45-R60 component type is used to simulate a curved conveyor. The
conveyor section forms a 90° arc. The component symbol cannot be scaled. The radius of the
arc is set to 60 pixels and cannot be changed. The effective radius of the component is
determined by the scale set for the chart. For example, a scale of 1 pix: 100 mm gives an
effective radius of 6 meters.
The speed at which objects are moved over this conveyor is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter).
Parameters
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The ConveyorCurve90-R60 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
Function
The ConveyorCurve90-R100 component type is used to simulate a curved conveyor. The
conveyor section forms a 90° arc. The component symbol cannot be scaled. The radius of the
arc is set to 100 pixels and cannot be changed. The effective radius of the component is
determined by the scale set for the chart. For example, a scale of 1 pix: 100 mm gives an
effective radius of 10 meters.
The speed at which objects are moved over this conveyor is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter).
Parameters
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The ConveyorCurve90-R100 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
Function
The ConveyorCurve90-R200 component type is used to simulate a curved conveyor. The
conveyor section forms a 90° arc. The component symbol cannot be scaled. The radius of the
arc is set to 200 pixels and cannot be changed. The effective radius of the component is
determined by the scale set for the chart. For example, a scale of 1 pix: 100 mm gives an
effective radius of 20 meters.
The speed at which objects are moved over this conveyor is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter).
Parameters
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The ConveyorCurve90-R200 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects on the conveyor section A – B. When the simulation is running the current transport
direction is indicated by green arrows in the symbol. The direction of transfer (to D or C) is also
indicated by green arrows.
The width of the symbol is scalable. The set width corresponds to the length of the 90-degree
transfer. As with all component types in the CONVEYOR library, the height of the symbol is
fixed at 40 pixels. The effective width of the 90-degree transfer is therefore determined by the
scale set for the chart.
The location of positions C and D for the transfer of objects can be moved. To do so, hold down
the ALT key and drag the connection point C or D with the mouse (with the left mouse button
held down) to the desired position.
Function
The 90DegreeTransfer component type is used to simulate a 90-degree transfer for moving
objects from conveyor section A – B to a conveyor connected at connector C or D without
rotating them.
The speed at which objects are moved over the conveyor section A – B is set at the hidden
analog input Speed of the component as a percentage of the configurable nominal conveyor
speed (NominalSpeed parameter). Correspondingly, the speed at which the objects are
transferred to the transfer section C – D is set at the hidden analog input TransferSpeed as a
percentage of the configurable nominal transfer speed (NominalTransferSpeed parameter).
The reference direction of the transfer sections is set from connector C to the transport section
or from the transport section to connector D.
Between one and four sensors can be positioned on the transfer relative to each of the four
connectors A, B, C and D. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NominalTransferSpeed
Nominal transfer speed; adjustable online
● PositioningAccuracy
Accuracy with which the object must be positioned for transfer to the transfer section
connecting to C or D
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol.
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol.
● NbrOfSensorsC
Number of sensors relative to connector C (1 to 4)
● SensorPositionC
Position of the corresponding sensor relative to connector C of the symbol.
● NbrOfSensorsD
Number of sensors relative to connector D (1 to 4)
● SensorPositionD
Position of the corresponding sensor relative to connector D of the symbol.
When the simulation is running, the defined sensors are shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The 90DegreeTransfer component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
You also need to specify how many objects can be present on the conveyor section at any one
time.
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) and the transfer speed as a percentage of the nominal
transfer speed (NominalTransferSpeed) using a slider and monitor the status of the maximum
eight sensors.
The extended operating window shows whether the object is close enough to connector C or
D to be transferred.
CrossOver – Crossover
Symbol
The two gray arrow heads in the symbol indicate the reference direction for movement of the
objects over sections A – B and C – D. When the simulation is running the current transport
direction is indicated by green arrows in the symbol.
The width of the symbol is scalable. The set width corresponds to the length of the crossover.
Function
The CrossOver component type simulates a crossover. The speed at which objects are moved
over this switch is set at the hidden analog input Speed of the component as a percentage of
the configurable nominal conveyor speed (NominalSpeed parameter).
The switch is operated by means of the two binary inputs Switch_CB_DA and Switch_AD_BC.
If the Switch_CB_DA input is set (True), the object is no longer transported over section A – B
but over section A – D (transport in reference direction) or section B – C (transport against
reference direction), depending on the transport direction. Correspondingly, if the
Switch_AD_BC input is set (True), the object is no longer transported over section C – D but
over section C – B (transport in reference direction) or over section A – D (transport against
reference direction), depending on the transport direction. Setting both inputs at the same time
deactivates the switch, which means that transport is stopped.
Parameters
The nominal speed at which the object is transported is set by means of the NominalSpeed
parameter. Its unit and default value are shown in the figure below.
Additional parameters
The CrossOver component includes the additional parameters TEMPLATE and HIERARCHY,
which can be used to control generation of the drive level. You can find additional information
on this in section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of the maximum eight
sensors.
In the extended operating window you can set the two binary inputs Switch_CB_DA and
Switch_AD_BC by means of a slider to set the transport direction of the crossover manually.
Lifter
A lifter is a conveyor section that can be moved vertically through several levels. In SIMIT a lifter
is made up of the base component of the LifterBase type and up to eight expansion
components of the LifterExtension type. The base component simulates the lifter in the base
level, while each additional level is simulated by an expansion component. A lifter that can be
moved through up to eight additional levels can be simulated in this way.
You do not have to position the base component and the associated expansion components on
the same chart. You can create a separate chart for each level, for example, and distribute the
lifter components over the individual charts.
The following points apply to the parameter assignment of the base component:
● There are no restrictions on the name of the base component.
● The NbrOfExtensions parameter indicates the number of additional levels and hence also
the number of expansion components used.
● In the base component you have to specify the position (LevelPosition) for each level, which
means the level above the base level in millimeters. The base level is by definition at level
zero. All level values must be positive and increase with the level number.
The following points should be borne in mind when assigning the parameters for the expansion
components:
● The name of the expansion component is formed from the name of the base component, the
'#' character, and a number indicating the level.
● The Level parameter must correspond to the level number. The numbering of the levels
starts with one.
● The BaseName parameter is the name of the base component.
● The length of the lifter is determined by the width of the base component.
Note
All expansion components must be exactly the same width as the base component. Otherwise,
a message will be displayed pointing to this inconsistency when the simulation is started.
The drives and the lifter sensors are fully implemented in the base component. This means
expansion components do not work without the base component.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. When the simulation is running the current transport direction is indicated by green
arrows in the symbol.
The width of the symbol is scalable. The set width corresponds to the length of the lifter.
Function
The LifterBase component type is used to simulate the base station of a lifter. The speed at
which objects are moved over the conveyor section is set at the hidden analog input Speed of
the component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter). Similarly, the lifting speed, which means the speed at which the lifter is moved to
the different levels, is set at the hidden analog input LifterSpeed as a percentage of the
configurable nominal lifting speed (NominalLifterSpeed parameter).
To move objects in and out at the various lifter levels, the lifter must be moved to the appropriate
level and stop flush with that level. Flushness must be set with a positioning accuracy Δ that is
the same for all levels (PositioningAccuracy parameter). The lifter stops flush with a level H if
the following applies for its level h:
H−Δ≤h≤H+Δ
Between one and four sensors can be positioned on the lifter relative to each of the two
connectors A and B. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Note
The base component has further hidden inputs for exchanging signals with extension
components. The corresponding signals are assigned to these inputs by default. Do not change
these default settings, otherwise the lifter components will not behave in the intended way in the
simulation.
Parameters
The behavior of the component is configurable.
● NominalSpeed
Nominal conveyor speed; adjustable online
● NominalLifterSpeed
Nominal lifting speed; adjustable online
● NbrOfExtensions
Number of additional levels (1 to 8)
● LevelPosition
Level of the corresponding additional level
● PositioningAccuracy
Positioning accuracy within which the level is deemed to have been reached.
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol.
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol.
When the simulation is running, the defined sensors are shown in the correct position in the
symbol. When a sensor is activated, its color changes to yellow.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The LifterBase component includes the additional parameters TEMPLATE and HIERARCHY,
which can be used to control generation of the drive level. You can find additional information
on this in section: Using templates (Page 803).
You also need to specify how many objects can be present on this conveyor section at any one
time.
Operating window
In the operating window, you can use a slider to set the transport speed as a percentage of the
nominal conveyor speed (NominalSpeed) and you can monitor the status of the sensors.
In the extended operating window you can move the lifter up or down by means of pushbuttons.
The current lifter position and level are displayed.
Symbol
The gray arrow head in the symbol indicates the reference direction for movement of the
objects. The width of the symbol is scalable. The set width corresponds to the length of the lifter
rail.
Note
The width of the extension component must be the same as the width of the base component.
Function
The LifterExtension component type is used to simulate a lifter at one of the accessible levels.
A component of this type can only be used in combination with a component of the LifterBase
type.
Parameters
The behavior of the component is configurable:
● Level
Level at which the component is located. The numbering starts at one.
● BaseName
Name of the corresponding base component
The parameters, their units and default values are shown in the figure below.
Additional parameters
Specify how many objects can be present on the section defined by the component at any one
time. This parameter should be set to the same value as for the base component.
Operating window
In the operating window, you can monitor the status of the maximum eight sensors.
Turntable-R60 – Turntable
Symbol
The gray arrow head in the symbol indicates the reference direction for transport of the object
on the turntable. When the simulation is running the current transport direction is indicated by
green arrows in the symbol.
Function
The Turntable-R60 component type simulates a turntable. A turntable rotates a conveyor
section through multiples of 90°. Using a turntable, objects can be transported onwards in the
original conveyor direction or at right angles to that direction.
The speed at which objects are moved on the turntable is set at the hidden analog input Speed
of the component as a percentage of the configurable nominal conveyor speed (NominalSpeed
parameter). Correspondingly, the rotation speed is set at the hidden analog input
RotationSpeed as a percentage of the configurable nominal rotation speed
(NominalRotationSpeed parameter).
The component symbol cannot be scaled. The radius of the turntable is thus fixed at 60 pixels
and cannot be changed. Correspondingly, the length of the turntable is fixed at 120 pixels. The
effective turntable length of the component is determined by the scale set for the chart. For
example, a scale of 1 pix: 100 mm gives an effective length of 12 meters.
Between one and four sensors can be positioned on the turntable relative to each of the two
connectors A and B. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NominalRotationSpeed
Nominal rotation speed; adjustable online
● PositioningAccuracy
Accuracy with which the turntable must be positioned for the object to be transferred
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol.
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The TurnTable-R60 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Specify how many objects can be located on the turntable at the same time.
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of the maximum 8
sensors.
In the extended operating window you can rotate the turntable manually by 90° in both
directions by means of pushbuttons. The end position in each case is displayed.
Symbol
The gray arrow head in the symbol indicates the reference direction for transport of the object
on the swivel table. When the simulation is running the current transport direction is indicated
by green arrows in the symbol.
Function
The Swiveltable-R120 component type simulates a swivel table that can be used to rotate a
conveyor section through 90°. Using a swivel table, objects can be transported onwards in the
original conveyor direction or at right angles to that direction.
The speed at which objects are moved on the swivel table is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter). Correspondingly, the rotation speed is set at the hidden analog
input RotationSpeed as a percentage of the configurable nominal rotation speed
(NominalRotationSpeed parameter).
The component symbol cannot be scaled. The radius of the swivel table, which means the
length of the swivel table, is fixed at 120 pixels and cannot be changed. The effective swivel
table length of the component is determined by the scale set for the chart. For example, a scale
of 1 pix: 100 mm gives an effective length of 12 meters.
Between one and four sensors can be positioned on the swivel table relative to each of the two
connectors A and B. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NominalRotationSpeed
Nominal rotation speed; adjustable online
● PositioningAccuracy
Accuracy with which the turntable must be positioned for the object to be transferred
● NbrOfSensorsA
Number of sensors relative to connector A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector A of the symbol.
● NbrOfSensorsB
Number of sensors relative to connector B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector B of the symbol.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The Swiveltable-R120 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Specify how many objects can be located on the swivel table at the same time.
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of the maximum 8
sensors.
In the extended operating window you can rotate the swivel table manually through 90° by
means of a pushbutton. Another pushbutton allows you to rotate it back to its original position.
Indicators show when it has reached the end position.
Symbol
The height and width of this component are scalable. The width sets the length of the transfer
carriage, the height sets the length of the transfer path.
The gray arrow head in the symbol indicates the reference direction for transport of the object
on the swivel table. When the simulation is running the current transport direction is indicated
by green arrows in the symbol.
Function
The TransferCarriage component type is used for simulating a transfer carriage. Objects can
be moved onto the transfer carriage from both sides. It can then be moved to another position
at right angles to the transport direction and the objects can then be transported onwards via
connectors Ai and Bi.
The number of connectors Ai, Bi present on the left and right of the component is configurable.
A maximum of 16 connectors on each side is possible; by default there are two connectors on
each side. A1, A2, B1, B2. Each connector marks a position that can be approached by the
transfer carriage at right angles to the transport direction.
The speed at which objects are transported on the transfer carriage is set at the hidden analog
input Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter). Correspondingly, the transfer speed is set at the hidden analog
input TransferSpeed as a percentage of the configurable nominal transfer speed
(NominalTransferSpeed parameter).
Between one and four sensors can be positioned on the transfer carriage relative to each of the
two connector sides A and B. When an object is within the detection range of a sensor, the
corresponding hidden binary output Sensor1 to Sensor4 is set. The ID of the detected object
can be obtained via the corresponding hidden integer outputs SensorId1 to SensorId4.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal conveyor speed; adjustable online
● NominalTransferSpeed
Nominal transfer speed; adjustable online
● PositioningAccuracy
Accuracy with which the transfer carriage must be positioned for the object to be transferred.
● NbrOfConnectorsA
Number of connectors on the left side (A)
● NbrOfConnectorsB
Number of connectors on the right side (B)
● NbrOfSensorsA
Number of sensors relative to connector side A (1 to 4)
● SensorPositionA
Position of the corresponding sensor relative to connector side A of the symbol.
● NbrOfSensorsB
Number of sensors relative to connector side B (1 to 4)
● SensorPositionB
Position of the corresponding sensor relative to connector side B of the symbol.
The parameters, their units and default values are shown in the figure below.
Additional parameters
The TransferCarriage component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
Specify how many objects can be located on the transfer carriage at the same time.
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider and monitor the status of the maximum 8
sensors.
In the extended operating window you can move the transfer carriage manually in both
directions to the next position by means of pushbuttons (Up, Down). The end position in each
case is displayed. Indicators show when the transfer carriage has reached a connector position
on one or the other side.
Symbol
The gray arrow head in the symbol indicates the reference direction for transport of the object
on the diagonal feed. When the simulation is running the current transport direction is indicated
by green arrows in the symbol.
Function
The SpurConveyor-1 component type simulates a diagonal feed with one spur. Objects can be
transported along section A – C or along the spur section A – B.
The speed at which objects are moved on the diagonal feed is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter). To switch conveying to the spur section, the hidden binary input
Switch is set to one (True).
Parameter
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The SpurConveyor-1 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in the section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider.
In the extended operating window you can change to the spur section by means of a switch.
Symbol
The gray arrow head in the symbol indicates the reference direction for transport of the object
on the diagonal feed. When the simulation is running the current transport direction is indicated
by green arrows in the symbol.
Function
The SpurConveyor-2 component type simulates a diagonal feed with two alternative spurs.
Objects can be transported along section A – C or along one of the two spur sections A – B or
A–D.
The speed at which objects are moved on the diagonal feed is set at the hidden analog input
Speed of the component as a percentage of the configurable nominal conveyor speed
(NominalSpeed parameter). To switch conveying to one of the two spur sections, one of the two
hidden binary inputs Switch_AB or Switch_AD is set to one (True): Switch_AB switches to spur
section A – B and Switch_AD switches to spur section A – D. If one of the two inputs is set,
setting the other one has no effect. There will be no switching to either spur section if both inputs
are set at the same time.
Parameter
The nominal conveyor speed can be set by means of a parameter. Its unit and default value are
shown in the figure below.
Additional parameters
The SpurConveyor-2 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in the section: Using templates (Page 803).
Operating window
In the operating window, you can set the conveyor speed as a percentage of the nominal
conveyor speed (NominalSpeed) using a slider.
In the extended operating window you can change to the corresponding spur section A – B or A
– D by means of a switch.
The MATERIAL directory of the CONTEC library contains component types for simulating
objects. Vehicles (Vehicle) can be used with component types in the RAILS directory to
simulate vehicular conveyor systems. Boxes (Box) can be used to simulate objects for
component types in the CONVEYOR directory.
You create material lists with these components. You can find more information on the topic in
the section: Scalability of objects (Page 800).
The size of a component (width and height of the symbol) is defined in the material list in
millimeters.
Symbol
Function
The Box component type is used to simulate an object with a rectangular outline, such as a
pallet or box. The component type defines the dimensions of the object. In the resolution 1:20
the standard dimensions correspond to the dimensions of a Euro pallet (1200 × 800 mm).
Symbol
Function
The CBox component type is used to simulate an object with a rectangular outline, such as a
pallet or box. The component type defines the dimensions of the object. In the resolution 1:20
the standard dimensions correspond to the dimensions of a Euro pallet (1200 × 800 mm).
When the simulation is running the symbol of a component of this type can be displayed in one
of 8 different colors. The color is determined with the three binary inputs R, G and B of the
component by mixing together the 3 primary colors red, green and blue.
Symbol
Function
The CBoxDS256 component type is used to simulate an object with a rectangular outline, such
as a pallet or box. The component type defines the dimensions of the object. In the resolution
1:20 the standard dimensions correspond to the dimensions of a Euro pallet (1200 × 800 mm).
When the simulation is running the symbol of a component of this type can be displayed in one
of 8 different colors. The color is determined with the three binary inputs R, G and B of the
component by mixing together the 3 primary colors red, green and blue.
In addition, a data storage with a configurable size (SizeOfStorage parameter) is defined for
components of this type. This memory represents the mobile data storage for an object. It is
created as a state vector MDS with the data type byte and can be up to 256 bytes in size.
Component types for writing to and reading this memory are located in the SENSORS library
in the RFID (Page 862) directory.
Parameters
The size of the data storage can be set by means of the SizeOfStorage parameter. The default
setting is one.
Vehicle
Symbol
Function
The Vehicle component type is used for simulating vehicles, such as those for electric overhead
monorail systems. The vehicle is assumed to have a rectangular outline. The component type
defines the dimensions of the outline. In the resolution 1:20 the standard dimensions
correspond to the dimensions of a Euro pallet (1000 × 300 mm).
The speed at which these vehicles move in the rail network in the simulation is generally
determined by the individual rail sections. However, the speed can also be set at the hidden
analog input Speed of the component as a percentage of the configurable nominal conveyor
speed (NominalSpeed parameter). The two speed settings for a component are added
together.
A component of this type can also be configured so that the vehicle starts off again with a delay
if it has previously been stopped by a holdup. This function is only effective if the speed is set
by the conveyor section.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal speed of the vehicle; adjustable online
● StartUpDelay
Start-up delay
● SensorRange
Detection range of the sensors
The parameters, their units and default values are shown in the figure below.
Additional parameters
The Vehicle component includes the additional parameters TEMPLATE and HIERARCHY,
which can be used to control generation of the drive level. You can find additional information
on this in section: Using templates (Page 803).
CVehicle
Symbol
Function
The CVehicle component type is used for simulating vehicles, such as those for electric
overhead monorail systems. The vehicle is assumed to have a rectangular outline. The
component type defines the dimensions of the outline. In the resolution 1:20 the standard
dimensions correspond to the dimensions of a Euro pallet (1000 × 300 mm).
The speed at which these vehicles move in the rail network in the simulation is generally
determined by the individual rail sections. However, the speed can also be set at the hidden
analog input Speed of the component as a percentage of the configurable nominal conveyor
speed (NominalSpeed parameter). The two speed settings for a component are added
together.
A component of this type can also be configured so that the vehicle starts off again with a delay
if it has previously been stopped by a holdup. This function is only effective if the speed is set
by the conveyor section.
When the simulation is running the symbol of a component of this type can be displayed in one
of 8 different colors. The color is determined with the 3 binary inputs R, G and B of the
component by mixing together the 3 primary colors red, green and blue.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal speed; adjustable online
● StartUpDelay
Start-up delay
● SensorRange
Detection range for sensors
The parameters, their units and default values are shown in the figure below.
Additional parameters
The CVehicle component includes the additional parameters TEMPLATE and HIERARCHY,
which can be used to control generation of the drive level. You can find additional information
on this in section: Using templates (Page 803).
Symbol
Function
The VehicleDS256 component type is used for simulating vehicles, such as those for electric
overhead monorail systems. The vehicle is assumed to have a rectangular outline. The
component type defines the dimensions of the outline. In the resolution 1:20 the standard
dimensions correspond to the dimensions of a Euro pallet (1000 × 300 mm).
The speed at which these vehicles move in the rail network in the simulation is generally
determined by the individual rail sections. However, the speed can also be set at the hidden
analog input Speed of the component as a percentage of the configurable nominal conveyor
speed (NominalSpeed parameter). The two speed settings for a component are added
together.
A component of this type can also be configured so that the vehicle starts off again with a delay
if it has previously been stopped by a holdup. This function is only effective if the speed is set
by the conveyor section.
In addition, a data storage with a configurable size (SizeOfStorage parameter) is defined for
components of this type. This memory represents the mobile data storage for a vehicle. It is
created as a state vector MDS with the data type byte and can be up to 256 bytes in size.
Component types for writing to and reading this memory are located in the SENSORS library
in the RFID (Page 862) directory.
Parameters
The behavior of the component can be set by means of parameters:
● NominalSpeed
Nominal speed; adjustable online
● StartUpDelay
Start-up delay
● SensorRange
Detection range for sensors
● SizeOfStorage
Size of the mobile data storage
The parameters, their units and default values are shown in the figure below.
Additional parameters
The VehicleDS256 component includes the additional parameters TEMPLATE and
HIERARCHY, which can be used to control generation of the drive level. You can find additional
information on this in section: Using templates (Page 803).
The RFID directory of the SENSORS library contains component types for simulating
identification systems that can be activated by the controller via the FC/FB45 in normal
operation. Other operating modes are not simulated. Components of these types enables data
exchange between the controller and the corresponding simulation components of objects.
You can find additional information on this in the section: Component types for simulating
objects (Page 856).
Both fixed data such as barcodes and write/read data in the case of a Moby can be exchanged.
All component types in the RFID directory have the same structure, but they differ in terms of
the number of channels available and the commands that are supported.
As communication between interface modules (ASM) and the controller takes place by means
of cyclical I/O data and non-cyclical records, the component types in the RFID directory can
only be used with couplings that support both methods of communication. These components
can therefore only be used with the PROFIBUS DP and PROFINET IO coupling. The first table
shows the interface modules supported for PROFIBUS DP, while the second table shows the
interface modules supported for PROFINET IO.
Operating principle
Simulated objects are managed in SIMIT as object components in material lists. Every object
component is automatically assigned a unique identifier (ID) at the start of the simulation, which
can be accessed via the simulated sensors of a conveyor section component. In addition, the
content of a mobile data storage (MDS) can be represented in object components. Accordingly,
the two component types CBoxDS256 and VehicleDS256 in the MATERIAL directory of
the CONTEC library have been created with data storage. In order to be able to exchange the
contents of a simulated data storage with the controller, components are needed in the
simulation that simulate the function of the corresponding interface module.
In the real system an interface module (ASM) is connected to a write/read device (SLG), which
is positioned at a certain point in the conveyor system. An object transported past that point is
detected by the SLG, and the SLG can read and in some cases also write to the object data
storage.
In SIMIT, the read/write devices (SLG) that are actually connected to the ASM and their
behavior are not simulated; only their functionality in terms of converting the data from the
mobile data storages in the ASM component types is simulated. As shown schematically in the
figure below, the identifiers (ID) of the objects as supplied by the simulated sensors on the
conveyor section are transmitted to the ASM components. Therefore the corresponding inputs
of the ASM components have to be implicitly connected to the simulated sensors.
,PSOLFLWFRQQHFWLRQV
$60VLPXODWLRQ
0DWHULDOKDQGOLQJ
VLPXODWLRQ
7UDQVSRUWHGPDWHULDO
&RQYH\RUOLQH
6HQVRU 6HQVRU
This ID is used to notify the controller via the cyclical input signal that an object has been
detected. Correspondingly, when the ASM component receives an acyclical command, it is
executed with the data from the MDS of the detected object. The data storage is accessed via
the ID.
All of the RFID component types contained in the CONTEC library include a simulation of the
"SIMATIC sensors – RFID systems" for communication with the STEP 7 function FB45 in
normal operation. Other operating modes of the RFID/Moby systems are not simulated and are
therefore not supported in the simulation.
The RFID components support the FB45 commands listed in the figure below.
Note
Not every RFID component type supports all the commands listed in the table. A description of
the commands supported by an RFID component type can be found in the description of that
component type.
A mobile data storage (MDS) is simulated in SIMIT in the form of a state array of the byte type,
which is created within the individual conveyor objects. This data is then accessed via the ID of
the detected conveyor object reported to the ASM component and the "MDS" parameter
configured in the ASM component. This parameter specifies the name of the state array to be
accessed. In this way you can define multiple and also different MDS for a conveyor object,
simply by storing details in the ASM component regarding which MDS is to be read or written
to. However, for the component types of objects with MDS provided in the CONTEC library
Signals are exchanged between RFID components and the controller both via input and output
words from the coupling for cyclical communication and acyclically via corresponding
communication functions implemented in the component type. For acyclical communication the
Unit input of the ASM component has to be connected to the Unit connector. The Unit connector
includes the subsystem number, the slave number and the slot number of the ASM from the
hardware configuration. Using drag-and-drop, it can be copied to the diagram from the
Hardware view in the property view of the SIMIT Unit coupling and connected to the ASM
component. When you configure the Unit connector manually, use the subsystem number, the
slave number and the slot number in the form "[#][#][#]".
The figure below shows an example of a hardware configuration with a four-channel interface
module that matches the view in the figure above.
Symbol
Function
The ASM452 component type simulates a 2-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 and AW2, EW2 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The ID1 and ID2 inputs
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 and MDS2 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 or ID2.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Additional parameters
The additional parameters comprise status values corresponding to the UDT110 as online
modifiable parameters for each of the two simulated read/write devices (SLG).
Operating window
The operating window shows the current states of the input and output words of the two
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for both channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM454 component type simulates a 4-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 to AW6, EW6 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The inputs ID1 to ID4
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 to MDS4 indicate which area of the MDS should be accessed by object
components via sensor ID1 to ID4. The figure below shows the parameters and their default
settings.
Operating window
The operating window shows the current states of the input and output words of the four
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the most recently executed command and
the associated command status for each of the four channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM456 component type simulates a 2-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 and AW2, EW2 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The ID1 and ID2 inputs
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 and MDS2 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 or ID2.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Additional parameters
The additional parameters comprise status values corresponding to the UDT110 as online
modifiable parameters for each of the two simulated read/write devices (SLG).
Operating window
The operating window shows the current states of the input and output words of the two
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for both channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM473 component type simulates a single-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data is exchanged with the
controller via the AW0, EW0 input/output. It should be linked to the relevant input/output signal
of the SIMIT Unit coupling. The ID1 input should be implicitly connected to the sensor of the
material handling simulation.
Parameters
Parameter MDS1 indicates which memory area of the MDS should be accessed by object
components via sensor ID1.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Additional parameters
The additional parameters comprise status values corresponding to the UDT110 as online-
editable parameters for the simulated read/write device (SLG).
Operating window
The operating window shows the current states of the input and output word that are accessed
by FB45. The bits shown in gray are not evaluated by an ASM component. The extended
operating window shows the antenna status, the most recently executed command and the
associated command status.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM475 component type simulates a 2-channel interface module for identification
systems on PROFIBUS DP or PROFINET IO. The commands listed in the table below are
supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 and AW2, EW2 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The ID1 and ID2 inputs
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 and MDS2 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 or ID2.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Additional parameters
The additional parameters comprise status values corresponding to the UDT110 as online
modifiable parameters for each of the two simulated read/write devices (SLG).
Operating window
The operating window shows the current states of the input and output words of the two
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for both channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM754 component type simulates a 4-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 to AW6, EW6 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The inputs ID1 to ID4
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 to MDS4 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 to ID4. The figure below shows the parameters and their
default settings.
Operating window
The operating window shows the current states of the input and output words of the four
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for each of the four channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM850 component type simulates a single-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data is exchanged with the
controller via the AW0, EW0 input/output. It should be linked to the relevant input/output signal
of the SIMIT Unit coupling. The ID1 input should be implicitly connected to the sensor of the
material handling simulation.
Parameters
Parameter MDS1 indicates which memory area of the MDS should be accessed by object
components via sensor ID1.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Operating window
The operating window shows the current states of the input and output word that are accessed
by FB45. The bits shown in gray are not evaluated by an ASM component. The extended
operating window shows the antenna status, the most recently executed command and the
associated command status.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The ASM854 component type simulates a 4-channel interface module for identification
systems on PROFIBUS DP. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 to AW6, EW6 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The inputs ID1 to ID4
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 to MDS4 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 to ID4.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Operating window
The operating window shows the current states of the input and output words of the four
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for each of the four channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The RF170C component type simulates a 2-channel interface module for identification systems
on PROFIBUS DP or PROFINET IO. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 and AW2, EW2 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The ID1 and ID2 inputs
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 and MDS2 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 or ID2.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Additional parameters
The additional parameters comprise status values corresponding to the UDT110 as online
modifiable parameters for each of the two simulated read/write devices (SLG).
Operating window
The operating window shows the current states of the input and output words of the two
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for both channels.
See also
Access to a data record or memory area (Page 188)
Symbol
Function
The RF180C component type simulates a 2-channel interface module for identification systems
on PROFINET IO. The commands listed in the table below are supported.
All inputs and outputs of the component types are integers. The ASM slave and module
address is set at the Unit input using the Unit connector. The cyclical data for each channel is
exchanged with the controller via the AW0, EW0 and AW2, EW2 inputs/outputs. It should be
linked to the relevant input/output signals of the SIMIT Unit coupling. The ID1 and ID2 inputs
should be implicitly connected to the sensors of the material handling simulation.
Parameters
Parameters MDS1 and MDS2 indicate which memory area of the MDS should be accessed by
object components via sensor ID1 or ID2.
The AntennaInitStatus parameter specifies the initial antenna status with which the SLG should
be initialized in the ASM at the start of simulation: True := antenna on, False := antenna off.
The figure below shows the parameters and their default settings.
Additional parameters
The additional parameters comprise status values corresponding to the UDT110 as online
modifiable parameters for each of the two simulated read/write devices (SLG).
Operating window
The operating window shows the current states of the input and output words of the two
channels that are accessed by FB45. The bits shown in gray are not evaluated by an ASM
component. The extended operating window shows the antenna status, the most recently
executed command and the associated command status for both channels.
See also
Access to a data record or memory area (Page 188)
The SIMIT component type editor CTE allows you to create your own component types, which
use the mechanisms of the conveyor technology simulation solution procedure. You can thus
expand the functions of the components supplied with the CONTEC library, for example, by
implementing more complex transport processes that are not covered by the supplied library
components and thus enhance your conveyor technology simulations. You can also create
your own component types from scratch to extend the CONTEC library and adapt it to your
specific conditions.
The topology of the modeled conveyor system is automatically determined when compiling a
simulation project from interconnected material handling components. Each component must
therefore provide relevant topological information about itself, which means information about
how it is to be treated topologically in the system. From a topological point of view it is necessary
to know how the reference directions for variables in a material handling system are defined for
a component and how data exchange between the component and the solution procedure is
set up.
Elements of the material handling system with topological information are:
● Segments of conveyor sections
● Branches
● Boundaries
Relationships with the topological connectors of the material handling component must be
defined for each of these elements. To do this, open the topology editor by double-clicking on
the Topology entry in the component type navigation menu.
&RQQHFWRUVRIW\SH
07
They can be joined by superimposing the connectors. Once linked, both connectors are hidden.
If topological connectors are connected with each other by a connecting line in the chart editor,
then the connected connectors are hidden. They are still visible only as pale shadows.
Connectors of the MT1 type cannot be joined more than once; they can only ever establish a
1:1 connection.
Topology of a segment
The topology description of a segment is used to set its reference direction. For example, the
definition
FROM a TO b;
defines a segment with a reference direction from the starting point a to the end point b. The
starting point and end point can be defined in the component type as a connector of type MT1
or as a branch or boundary.
Speeds are positive in the reference direction. The reference direction is also the preferred
direction, which is used by the solution procedure to determine the calculation order.
Topology of a branch
A branch as an internal node in a component type is defined as follows in the topology
description:
INTERNAL_NODE i;
The topological connectors of the component must also be assigned to this branch. Three
connectors can be assigned in the topological description as per the example below:
FROM i TO a;
FROM i TO b;
FROM i TO c;
The three connectors a, b and c must be defined as type FLN1 connectors in the component
type. The figure below shows a diagram of the resulting topological structure of the component
type:
A branch can also be defined as multiple segments having a common starting or end point that
is defined as an MT1 topological connector.
Topology of a boundary
In the topological description of a component type a boundary point as an external node e is
defined as follows:
EXTERNAL_NODE e;
This external node must be also be linked to at least one topological connector of the
component. The topology description is, for example, to be completed as
FROM e TO a;
. The topological connector a must be defined in the component type as a connector of type
MT1. The figure below shows a diagram of the resulting topological structure of the component
type.
6HFWLRQLQDFWLYH 6HFWLRQLQDFWLYH
6HFWLRQDFWLYH 6HFWLRQDFWLYH
'LUHFWLRQRIPRWLRQ
'LUHFWLRQRIPRWLRQ
The segments, branches and boundary points of a component and the solution procedure for
the material handling exchange data via special connectors. There are seven different
connection types MT2 to MT8 available for this purpose. Their use in material handling
components is explained in the sections below.
&RQYH\RUWHFKQRORJ\FRPSRQHQWV
6ROXWLRQPHWKRGIRUFRQYH\RUWHFKQRORJ\
Connectors of connection types MT2 to MT8 establish a connection to the solution procedure
and must therefore be set as hidden on the component symbol. In the connector properties, the
usage "Only in property view" or "Only in CTE" must be set.
Connectors of connection type MT2 to MT7 should be defined in the OUT direction, a connector
of connection type MT8 in the IN direction.
See also
Connection type MT2 for segments (Page 897)
Connection type MT3 for stoppers (Page 898)
Connection type MT4 for sensors (Page 898)
Connector type MT5 for placing objects (Page 899)
Connection type MT6 for positions (Page 900)
Connector type MT7 for parameter assignment of objects (Page 901)
Connector type MT8 for transferring objects at boundary points (Page 902)
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
D E
0707
072FFXSLHG 07$QJOH
076SHHG
07)RUZDUG&RQGLWLRQ
07%DFNZDUG&RQGLWLRQ
6ROXWLRQPHWKRG
The output signals for the segment are set or calculated in the component and sent to the
solution procedure:
1. Angle (integer)
The angle in degrees of the segment of a circle that describes this segment. Positive angles
rotate in a clockwise direction, negative angles rotate in a counterclockwise direction. For a
straight connection the angle should be set to zero.
This setting is only evaluated when the simulation is initialized; changing the value during
the cyclical calculation has no effect.
2. Speed (analog)
The speed in m/s at which objects are to be moved over this segment. Positive values move
it in the preferred direction, negative values move it against the preferred direction.
3. ForwardCondition (integer)
Specifies whether this segment is active in the preferred direction (0) or not (–1).
4. BackwardCondition (integer)
Specifies whether this segment is active against the preferred direction (0) or not (–1).
The component receives information about the conveyor section from the solution procedure
via the input signal:
1. Occupied (bool)
Specifies whether the outline of one or more objects is in contact with this segment.
Connection type MT2 is used in the Rail-S4 and Conveyor-S4 library components, for example.
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
D E
0707
073RVLWLRQ
07$FWLYH
6ROXWLRQPHWKRG
The output signals for the segment are set or calculated in the component and sent to the
solution procedure:
1. Position (analog)
The position of the stopper on the segment as a percentage of the total
length of the segment.
This setting is only evaluated when the simulation is initialized; changing the value during
the cyclical calculation has no effect.
2. Active (binary)
Indicates whether the stopper is active (True) or inactive (False).
Connector type MT3 is used in the Conveyor-S4-Stopper library component, for example.
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
D E
0707
072EMHFW,' 073RVLWLRQ
6ROXWLRQPHWKRG
The output signals for the segment are set or calculated in the component and sent to the
solution procedure:
1. Position (analog)
The position of the sensor on the segment as a percentage of the total length of the
segment.
This setting is only evaluated when the simulation is initialized; changing the value during
the cyclical calculation has no effect.
The component receives information about the segment from the solution procedure via the
input signal:
1. ObjectID (integer)
The ID of the object that is currently detected by the sensor. If no object is detected, this
value is zero.
Connection type MT4 is used in the Rail-S4 and Conveyor-S4 library components, for example.
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
D E
0707
072EMHFW,' 07&OHDUDQFH
072YHUODS
077UDQVIHU
6ROXWLRQPHWKRG
The output signals for the segment are set or calculated in the component and sent to the
solution procedure:
1. ObjectID (integer)
The ID of the object to be placed on this segment. The component generally obtains this ID
by means of appropriate function calls. You can find information on this in the following
sections:
– _MT.GetObjectByName (Page 905)
– _MT.GetObjectByType (Page 905)
2. Overlap (analog)
Overlap in millimeters in the preferred direction. This can be used to move the placement
position in relative terms. The placement position must always be on the segment, however.
3. Transfer (bool)
When this signal is set to True, the solution procedure starts the placement process. The
component can only set the signal for exactly one cycle, after which it must return to False.
The component receives information about the segment from the solution procedure via the
input signals:
1. Clearance (analog)
The available length of segment in millimeters viewed in the preferred direction.
Connection type MT5 is used in the Rail-S4 and Conveyor-S4 library components, for example.
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
LH
0707
07;3RVLWLRQ
07<3RVLWLRQ
6ROXWLRQPHWKRG
The output signals for the node are set or calculated in the component and sent to the solution
procedure:
1. XPosition (analog)
The X position of the node in millimeters relative to the top left corner of the component.
This setting is only evaluated when the simulation is initialized; changing the value during
the cyclical calculation has no effect.
2. YPosition (analog)
The Y position of the node in millimeters relative to the top left corner of the component.
This setting is only evaluated when the simulation is initialized; changing the value during
the cyclical calculation has no effect.
5HYHUVH
LQEDFN LQIURQW
)RUZDUG
The connector of type MT7 must always be defined in the OUT direction. It connects the
component to the solution procedure to exchange various variables that are relevant to the
object between the solution procedure and the component.
A component can have no more than one MT7 type connector.
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
0707
07$EV3RVLWLRQ 076SHHG
07)URQW+ROGXS 076WDUW8S'HOD\
075HDU+ROGXS 076HQVRU5DQJH
6ROXWLRQPHWKRG
The output signals for the object are set or calculated in the component and sent to the solution
procedure:
1. Speed (analog)
The speed of the object established by its drive in m/s. A positive speed moves the vehicle
forwards, a negative speed moves it backwards.
This speed is replaced by a speed set by the rail if applicable.
2. StartUpDelay (analog)
The start-up delay in seconds. If the object is held up by the solution procedure, the object
waits for this time before moving again once the hold-up is cleared.
3. SensorRange (analog)
The percentage of the object length that is detected by a sensor. This value must be
between 0 and 100%.
The component receives information about the object from the solution procedure via the input
signals:
1. AbsPosition (analog)
Reserved for subsequent development.
2. FrontHoldup (binary)
If this signal is set to True, there is a stopper or another object directly in front of the object.
3. RearHoldup (binary)
If this signal is set to True, there is a stopper or another object directly behind the object.
Connector type MT7 is used in the Vehicle (Page 858) library component, for example.
The figure below shows the input and output signals with the direction of data exchange
between the component and the solution procedure.
H
0707
07$EV3RVLWLRQ 072XW2IIVHW
07;3RVLWLRQ 072XW2EMHFW,'
07<3RVLWLRQ 072XW7ULJJHU
07,Q2IIVHW 072XW6SHHG
07,Q2EMHFW,' 072XW2IIFXW
07,Q7ULJJHU
07,Q6SHHG
07,Q2IIFXW
6ROXWLRQPHWKRG
The output signals for the external node are set or calculated in the component and sent to the
solution procedure:
1. OutOffset (analog)
The length of the available section, viewed from the connector into the component. A
negative value means that viewed from the component, an object is projecting onto the
adjacent section controlled by the solution procedure; in this case the value corresponds to
the length of the projecting part of the object. All values are given in millimeters.
2. OutObjectID (integer)
The object ID of the object that viewed from the component is projecting onto the adjacent
section controlled by the solution procedure. The value is zero if no object is projecting.
3. OutTrigger (binary)
The component sets this signal to True for exactly one cycle to show that the adjacent
section controlled by the solution procedure has to take over the object.
4. Out.Speed (analog)
The speed in m/s at which the object is transferred.
5. OutOffcut (analog)
The time that the current cycle could not include because the object had reached the
transfer node, measured in seconds. The solution procedure has to take this time into
account in the next cycle to calculate an additional movement.
The component receives information from the solution procedure via the input signals:
1. AbsPosition (analog)
Reserved for subsequent developments.
2. XPosition (analog)
The relative X position of the connector linked to the node relative to the top left corner of the
component in millimeters.
3. YPosition (binary)
The relative Y position of the connector linked to the node relative to the top left corner of the
component in millimeters.
4. InOffset (analog)
The length of the available section, viewed from the component connector, in the direction
of the adjacent section outside the component. A negative value means that viewed from
the adjacent section controlled by the solution procedure, an object is projecting into this
component; in this case the value corresponds to the length of the projecting part of the
object. All values are given in millimeters.
5. InObjectID (integer)
The object ID of the object that viewed from the section controlled by the solution procedure
is projecting into the component. The value is zero if no object is projecting.
6. InTrigger (binary)
The solution procedure sets this signal to True for exactly one cycle to show that the
component has to take over the object.
7. InSpeed (analog)
The speed in m/s at which the object was last moved by the solution procedure.
8. InOffcut (analog)
The time that the current cycle could not include because the object had reached the
transfer node, measured in seconds. The component has to take this time into account in
the next cycle in order to calculate an additional movement.
Connector type MT8 is used in the TransferCarriage library component, for example.
If you create your own component types you can utilize various system functions to access
objects in the simulation.
All functions described below return an error code as the return value. In order for a function to
be able to supply return values in a variable that is passed, this variable must be defined as a
field (vector), in this case with the dimension one. Refer to the table below for the meaning of
this return value.
Value Meaning
0 No error
−2 The object cannot be positioned directly because it is currently under solution procedure
control.
−3 The object cannot be positioned or rotated because it is not currently assigned to a con‐
veyor section.
Value Meaning
−10 There is no object with the specified ID.
−11 The object with the specified ID is not available.1)
−12 There is no object with the specified name.
−13 The object with the specified name is not available.
−14 There is no object of the specified type.
−15 An object of the specified type is not available.
−20 The component has no signal with the specified name.
−21 The specified signal type cannot be used in this context.
−22 The address range of the byte array to be read or written has been exceeded.
−1000 General error
1
An object is not available if it is reserved for being assigned to a conveyor section or if it is assigned
to a conveyor section.
_MT.GetObjectByName
The _MT.GetObjectByName function returns the ID of the object with the instance name name
if it is available as an object, otherwise it returns the value –1. The return value type is long.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● name (string)
The instance name of the object.
_MT.GetObjectByType
The _MT.GetObjectByType function returns the ID of an object of component type type if it is
available as an object, otherwise it returns the value –1. The return value type is long.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● type (string)
The type of object required.
● store (string)
The name of the material list in which the object is located. If an empty string is passed here,
all existing lists are searched.
_MT.Restore
The _MT.Restore function releases an object. The return value is void.
_MT.GetWidth
The _MT.GetWidth function returns the width of an object in millimeters. The return value type
is double.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
_MT.GetHeight
The _MT.GetHeight function returns the height of an object in millimeters. The return value type
is double.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
_MT.GetDepth
The _MT.GetDepth function returns the depth of an object in millimeters. The return value type
is double.
_MT.GetAngle
The _MT.GetAngle function returns the angle in degrees of an object relative to the tangent of
the segment on which it is located (−180° .. +180°). The return value type is integer.
Note that this function can only be called for objects that are assigned to a conveyor section.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
_MT.SetPosition
The _MT.SetPosition function sets the position of an object relative to the position of the
conveyor section component to which this object is assigned. The position is specified in
millimeters relative to the top left corner of the component (in its starting position). The return
value type is void.
Note that this function can only be called for objects that are assigned to a conveyor section but
are not under solution procedure control.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be changed.
● x (analog)
X position in millimeters relative to the conveyor section component.
● y (analog)
Y position in millimeters relative to the conveyor section component.
_MT.SetAngle
The _MT.SetAngle function sets the angle in degrees of an object relative to the tangent of the
segment on which it is located (−180° .. +180°). The return value type is void.
Note that this function can only be called for objects that are assigned to a conveyor section.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be changed.
● angle (integer)
Angle in degrees relative to the tangent of the segment.
_MT.AddAngle
The _MT.AddAngle function increases the angle in degrees of an object relative to the tangent
of the segment on which it is located (−180° .. +180°). The return value type is void.
Note that this function can only be called for objects that are assigned to a conveyor section.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be changed.
● angle (integer)
Angle in degrees relative to the tangent of the segment.
_MT.SetHoldup
The _MT.SetHoldup function transfers to an object information about whether it is positioned
directly in front of or behind a stopper or another object. The return value type is void.
Note that this function can only be called for objects that are assigned to a conveyor section but
are not under solution procedure control.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be changed.
● front (binary)
Information as to whether the object is blocked in front.
● rear (binary)
Information as to whether the object is blocked to the rear.
_MT.GetBinaryValue
The _MT.GetBinaryValue function is used to query a binary variable (state, input, output) of an
object. The return value type is bool.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
● property (string)
The name of the variable to be queried
_MT.GetAnalogValue
The _MT.GetAnalogValue function is used to query an analog variable (discrete state, input,
output) of an object. The return value type is double.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
● property (string)
The name of the variable to be queried.
_MT.GetIntegerValue
The _MT.GetIntegerValue function is used to query an integer variable (state, input, output) of
an object. The return value type is long.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
● property (string)
The name of the variable to be queried.
_MT.GetByteValue
The _MT.GetByteValue function is used to query a byte (state) of an object. The return value
type is byte.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
● property (string)
The name of the state to be queried.
_MT.GetByteArray
The _MT.GetByteArray function is used to query a byte array (state) of an object. The return
value type is void.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be queried.
● property (string)
The name of the state vector to be read.
● stateoffset (long)
The offset in bytes from which the state vector is to be read.
● buffer (byte[])
Byte array in which the read byte is to be entered. If you specify a state vector for the
component, enter it in the notation for new state values, which means prefixed with "@".
● bufferoffset (long)
The offset in bytes from which the read bytes are to be entered.
● count (long)
The number of bytes to be read.
Note
All arrays must be large enough to execute this operation; otherwise, unpredictable errors
could occur in the simulation process.
_MT.SetBinaryValue
The _MT.SetBinaryValue function is used to write a binary variable (state, input) of an object.
The return value type is void.
_MT.SetAnalogValue
The _MT.SetAnalogValue function is used to write an analog variable (discrete state, input) of
an object. The return value type is void.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be described.
● property (string)
The name of the variable to be written.
● value (double)
The value to be written.
_MT.SetIntegerValue
The _MT.SetIntegerValue function is used to write an integer variable (state, input) of an object.
The return value type is void.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be described.
● property (string)
The name of the variable to be written.
● value (long)
The value to be written.
_MT.SetByteValue
The _MT.SetByteValue function is used to write a byte (state) of an object. The return value
type is void.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be described.
● property (string)
The name of the state to be written.
● value (byte)
The value to be written.
_MT.SetByteArray
The _MT.SetByteArray function is used to write a byte array (state) of an object. The return
value type is void.
Specify values for the following parameters:
● error (long[])
Error code
You can find information about the error code in the table in the section: System functions
(Page 904).
● id (long)
The ID of the object to be described.
● property (string)
The name of the state vector of the object to be described.
● stateoffset (long)
The offset in bytes from which the state vector is to be written.
● buffer (byte[])
Byte array containing the byte to be written.
● bufferoffset (long)
The offset in bytes from which the byte array is to be transferred.
● count (long)
The number of bytes to be written.
Note
All arrays must be large enough to execute this operation; otherwise, unpredictable errors
could occur in the simulation process.
See also
Options > Assign coupling signals (Page 925)
● Automated import
Imports models from the following sources:
– XML (Page 263)
– ZIP (Page 270)
You can find additional information in the section Automated import (Page 262).
● Bulk engineering import
Transfer the parameters and input defaults from a table to existing charts. You can find
additional information on this in section: Bulk engineering (Page 271).
● Help
This is where you access the SIMIT online help.
See also
Table import (Page 252)
IEA import (Page 256)
CMT import (Page 258)
Here, you can create a new project. Enter the required data for this and make the settings in the
input fields.
● Project name
Enter a name for your project or accept the default name here.
● Target folder
The storage location of the new project is preset here. Click "..." to select a different storage
location.
● Author
You can change the name of the author here. This entry is optional.
● Comment
You can enter a comment of your choice about the project here. This entry is optional.
Click "Create" to create the new project and close the dialog box.
The most recent projects and the sample project are listed here. The project name, location and
date of the last update of the project are also displayed for each project. This information cannot
be changed here.
If the desired project is not displayed here, you can search for it by clicking "Browse ...".
Open the project by selecting it and clicking the "Open" button.
Note
An archived SIMIT project can contain executable code. Only retrieve projects from a
trustworthy source.
Note
Initialization does not start simulation.
Before the simulation starts, you are asked whether you want to save the changes to the project
and the consistency check is performed.
See also
Addressing a signal symbolically (Page 207)
In this dialog box, you make the following settings for importing the hardware configuration:
● "SDB import"
Defines the folder in which the system data blocks for importing the hardware configuration
of an S7-300/S7-400 station are located.
● "OMS import"
Defines the folder in which the system data blocks for importing the hardware configuration
of a S7-1200/S7-1500 station are located.
The OMS import is supported as of STEP 7 V13 and higher.
● "XML import"
Specifies the file from which a vendor-neutral hardware configuration with PROFIBUS and/
or PROFINET master systems is imported.
You can find information on the structure of this file under "XML import interface (Page 99)".
● "Configuration file"
Specifies the storage location of the configuration file with additional device information.
Only relevant for "SDB import".
Symbol mode Stations of the PLCSIM Advanced coupling Stations of the PLCSIM Ad‐
are imported again (updated) vanced coupling are cre‐
ated again
Create new All symbols of the stations to be imported are All symbols of the stations
deleted and the new symbols from the import to be imported are applied
are applied. from the import.
Overwrite All symbols of the stations to be imported are
applied from the import. Existing symbols are
overwritten. New symbols are applied.
Add Only those symbols are applied from the im‐
port of the stations to be imported for which no
prior symbols existed.
Ignore The symbols of the stations to be imported are The symbols of the sta‐
not applied. Existing symbols remain un‐ tions to be imported are not
changed. applied.
● Stations >>
Shows the area for station selection from the selected project. The stations are read in from
the selected project. Only S7-1500 stations that are supported by PLCSIM Advanced are
shown.
All supported stations of the STEP 7 project are selected by default.
● Import
Starts station import to the SIMIT project.
● Cancel
Cancels the import. Only the "PLCSIM Advanced" folder is created in the project navigation.
See also
Creating a coupling of the "PLCSIM Advanced" type (Page 140)
Importing hardware configuration to station (Page 141)
This dialog box allows you to make the following settings to import the hardware configuration
of a STEP 7/PCS 7 project:
● STEP 7/PCS 7 multiproject / STEP 7/PCS 7 project
Specifies the project from which the hardware configuration is imported. These options are
only available if SIMATIC Manager is installed.
● HWCNExport file
Specifies the HWCNExport file from which the hardware configuration is to be imported.
● Symbols
Specifies how symbol names for inputs and outputs are treated. The selection is only
effective if symbol names are assigned in the STEP 7/PCS 7 project.
Symbol mode Virtual controller is imported again (updated) Virtual controller is created
Create new All symbols of the virtual controllers to be im‐ All symbols of the virtual
ported are deleted and the symbols from the controllers to be imported
import saved. are taken from the import.
Overwrite All symbols of the virtual controllers to be im‐
ported are taken from the import. Existing sym‐
bols are overwritten. New symbols are applied.
Add Symbols are only taken from the import for vir‐
tual controllers for which no symbols have yet
been saved.
Ignore The symbols of the virtual controllers to be im‐ The symbols of the virtual
ported are not applied. Existing symbols re‐ controllers to be imported
main unchanged. are not applied.
See also
Creating a HWCN export file (Page 62)
Importing a STEP 7/PCS 7 project (Page 126)
Creating a Virtual Controller (Page 125)
Open the dialog box by clicking on the "STL import" button on the "DB" tab in the virtual
controller coupling editor.
The following settings are made in this dialog box:
● "STL sources"
Specifies the STL source
● "Symbol table (opt.)"
Specifies the symbol table.
If the data blocks in the STL source have symbolic names, the system can establish the data
block number if you specify the symbol table. The numbers of the data blocks are read in
from the symbol table and displayed in the dialog box under "Data block number".
● "Data block name"
For import from a symbol table, specifies the data block from which a memory area is to
imported.
● "Data block number"
Specifies the data block number from which a memory area is to imported.
Data block numbers entered manually are not validated. When you import from a symbol
table, the data block number is already entered.
● "Direction"
Specifies when input or output signals are imported.
● "Start byte"
Specifies the start byte from which the signals are imported.
● "End byte"
Specifies the end byte up to which the signals are imported. Here, you enter, at most, the
end of the data block.
● "Import"
Starts the import. The following fields must be filled out:
– STL source
– Data block number
– Start byte
– End byte
Any existing signals in the specified memory area of "Start byte" and "End byte" are
overwritten.
See also
Importing DB data from STL sources (Page 138)
In this dialog box, you make the following settings for importing signal properties:
● "Format"
The format that can be read depends on the current coupling type. The following file formats
are read in:
– SIMATIC symbol table from STEP 7 or PCS 7
You can find additional information in section: Symbol table (Page 193).
– PLC tag table from the TIA Portal
You can find additional information in section: Variable table (Page 194).
– Signal table (txt file)
You can find additional information in section: Signal table (Page 195).
Note
OPC coupling
If signal properties were saved in txt format, the file also contains SIMATIC addresses
and information for scaling. However, this information cannot be processed by an OPC
coupling. If a txt file is imported into a OPC connection, the only information included is
that which an OPC coupling can also process.
– INI file
You can find additional information in: INI format of the OPC couplings (Page 196)
● "File"
Specifies the storage location of the import file.
● ""Which properties do you want to import?" area"
Specifies which signal properties are to be imported. You can only import the signal
properties that are in the import file. The following signal properties are imported by default
when you import a symbol table or tag table:
– Address
– Symbol
– Data type
– Comment
● "Mode"
The mode determines how the signals already present in the coupling and their properties
are processed. The import modes that can be selected depends on the current coupling
type.
Note
The import modes "New signals" and "Add signals" are supported by the following coupling
types:
● SHM
● OPC
● PLCSIM
● PRODAVE
The import modes "New properties", "Overwrite properties" and "Add properties" are
supported by all coupling types.
The following import modes are available:
– New signals
All existing signals are deleted and new signals are created with the imported
information. The only properties imported are the once activated in the "Which properties
do you want to import?" area. All other properties retain their default settings.
– Add signals
All signals from the import file are added. The only properties imported are the once
activated in the "Which properties do you want to import?" area. All other properties
retain their default settings. Already existing signals are not changed.
– New properties
The properties selected in the "Which properties do you want to import?" area are set to
their default values for all signals available in the coupling and then taken from the import
file.
– Overwrite properties
All properties selected in the "Which properties do you want to import?" area are taken
from the import file and applied to the existing signals.
– Add properties
All properties selected in the "Which properties do you want to import?" area that still
have their default settings are taken from the import file and applied to the existing
signals.
● "Adapt data width"
Note
This checkbox is only available for the following coupling types:
● SIMIT Unit
● Virtual controller
● PLCSIM Advanced
Specifies that the data width of signals is to be automatically adjusted to data width specified
in the import file upon import. You can find additional information in section: Converting the
data width of signals (Page 189).
If the check box is not selected and the width of the data to be imported does not match the
existing signal, this signal is not imported.
In this dialog box, you make the following settings for exporting signal properties:
● "Type"
Specifies the file format of the export file. The file format depends on the coupling type
whose signal properties you are exporting.
– SIMATIC symbol table from STEP 7/PCS 7 (seq file)
This format only contains the signals from the coupling for which a symbolic name has
been assigned.
You can find additional information in section: Symbol table (Page 193).
– Signal table (txt file)
This format contains all signals from the coupling.
You can find additional information in section: Signal table (Page 195).
– INI format
Note
OPC coupling
Since OPC signals do not have an address nor can they be transmitted as scaled raw
values, the signal table can only be filled to a limited extent. Such a signal table can be
imported into another OPC coupling, but import into couplings that expect SIMATIC
signals is not possible.
● "File"
Specifies the storage location of the export file.
Note
SIMIT manages all information in this folder that is relevant for the project. Note the following:
● Do not rename this folder.
● Do not change any files in this folder.
● Do not save any files in this folder.
● Do not create any files in this folder.
"Device description PROFIBUS (GSD)" and "Device description PROFINET (GSDML)" tabs
These tabs list the devices supported by the SIMIT Unit. You can expand the list of supported
devices by importing device descriptions. You can find additional information in
section: Importing device description file to SIMIT (Page 84).
● Refresh
Refreshes the view.
● Import
Opens a dialog box for importing device descriptions from a device description file.
● Delete
Removes a device imported from a device description file from the list.
You can make the following settings for instantiating a template in this dialog box:
● "Import file"
Specifies that the templates are instantiated from a file.
Specifies the import file. The following file types can be imported: *.txt, *.xls, *.xlsx, *.iea;
*.xml.
● "Simulation model"
Specifies that the templates are instantiated from the simulation model.
● "Coupling"
Specifies the coupling.
● "Template folder"
Specifies the folder in which the search for the SIMIT templates referenced in the CMT file
is to take place.
The name of the CMT type specified in the CMT file must exactly match the name of the
template used in SIMIT.
● "Template"
Specifies the storage location of the template.
● "Separator"
Specifies the separator.
● "Grouping"
Specifies the grouping.
● "Maximum width"/"Maximum height"
Specifies the width/height in pixels.
● "Remove elements with empty replacement"
Specifies if empty replacements are to be removed from the file.
● "Preview >>"
Shows a preview of the import.
On the left in the preview, you can see the newly created folders and charts from the import.
Individual folders and charts can be deselected. If you select a chart on the left, you will see
the replacements to be performed on the right. The template used in each case is entered
in the second header on the right and an indication is given if a template has been found at
all.
● "Import"
Starts the import.
See also
Instantiating templates from files (Page 251)
Instantiating templates from the simulation model (Page 261)
The following settings for automatic parameter assignment and bulk data import are made in
this dialog box:
● "Apply changes from last simulation"
Specifies whether the changes from the most recently active simulation for this project are
to be applied automatically.
The check box is only enabled if at least one simulation has already been run for the project.
Disable this option to import bulk data.
● "Table"
Specifies the file from which the data is read.
● "Parameter"
Specifies whether the parameters from the table are to be applied.
● "Inputs"
Specifies whether the input defaults from the table are to be applied.
● "Controls"
Specifies whether the default control settings from the table are to be applied.
● "Preview >>"
Displays a preview of automatic parameter assignment.
● "Import"
Runs automatic parameter assignment/Imports the modified values.
You can find additional information on this in section: Importing data (Page 273).
Open the dialog box by pressing the shortcuts <Ctrl+F> for "Find" or <Ctrl+H> for "Replace".
The search is limited to the area in which you opened the dialog box.
The following settings are made in this dialog box:
● "Find"
Specifies the search term.
● "Find Next"
Searches for the next occurrence of the search term.
● "Replace with"
Specifies the term that will replace the search term.
● "Replace"
Replaces the found search term.
The "Find Next" function is automatically executed next.
● "Replace all"
Replaces all search terms found.
● "Options"
Shows a configuration area in which you can enable additional options.
Supported are, for example, "regular expressions" or "placeholders". The following
characters can serve as placeholders:
– "?": Represents a variable character. The search term "H?llo", for example, finds "Hello"
and "Hallo"
– "*": Represents any number of variable characters
This menu command displays the following information about your SIMIT installation:
● Version
● Version of the SU software
● Version of SIMIT Virtual Controller (VC) (if installed)
Select a printer from the drop-down list and set the number of copies.
Click the "Settings ..." button to change the settings of the selected printer.
Click "Print" to start printing and close the dialog box.
See also
Printing charts (Page 223)
Printing trends (Page 288)
In this dialog box, the parameters of the selected template are listed in the "Placeholder"
column. Arbitrary values can be entered as replacements in the "Replacement" column.
Select the "Remove elements with empty replacement" check box to remove parameter in the
template for which you have not entered a name in the "Replacement" column.
Click "OK" to apply the changes and close the dialog box.
Select a new coupling in this dialog box. The following couplings are available for selection:
● SIMIT Unit
You can find additional information on the coupling under SIMIT Unit (Page 64).
● Virtual controller
You can find additional information on the coupling under Virtual Controller (Page 105).
● PLCSIM Advanced
You can find additional information on the coupling under PLCSIM Advanced coupling
(Page 140).
● PLCSIM
You can find additional information on the coupling under PLCSIM coupling (Page 145).
● OPC DA server
You can find additional information on the coupling under OPC coupling (Page 147).
● OPC DA client
You can find additional information on the coupling under OPC coupling (Page 147).
● OPC UA client
You can find additional information on the coupling under OPC coupling (Page 147).
● Shared memory
You can find additional information on the coupling under Shared memory coupling
(Page 162).
● PRODAVE
You can find additional information on the coupling under PRODAVE coupling (Page 172).
● MCD
You can find additional information on the coupling under MCD coupling (Page 175).
Click "OK" to confirm the selection and close the dialog box.
You can enter the names for elements of custom enumeration type in this dialog box.
You can find additional information in the section: The "Enumeration Types" task card
(Page 326).
You can create new components or open existing ones in this dialog box. To do this, select the
desired function.
Click the "Browse..." button to select the storage location of the component.
Click the "Open" button to open the component in the editor.
Select the check box "Always show this dialog on startup", if this dialog box is to open
automatically when you start the CTE.
You define the signals of custom connection type in this dialog box. You select the data type of
the signal from the drop-down list. You can create any number of signals.
Select the check box "Multiple connection", if one output is to be connected with more than one
input.
You can find additional information in the section: The "Connection Types" task card
(Page 327).