what's new in simit v7.1? · figure 4-28: diagnostics in the properties dialog for macro components...

s

SIMIT 7

What's New In SIMIT V7.1?

Manual

s

Edition

January 2013

Siemens offers simulation software to plan, simulate and optimize plants and machines. The simulation- and optimization-results are only non-binding suggestions for the user. The quality of the simulation and optimizing results depend on the correctness and the completeness of the input data. Therefore, the input data and the results have to be validated by the user.

Trademarks

SIMIT® is a registered trademark of Siemens AG in Germany and in other countries.

Other names used in this document can be trademarks, the use of which by third-parties for their own purposes could violate the rights of the owners.

Copyright © Siemens AG 2013 All rights reserved

The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages.All rights, including rights created by patent grant or registration or a utility model or design, are reserved. Siemens AG Industry Sector Industry Automation Division Process Automation SIMIT-HB-V7ACI-2013-01-en

Exclusion of liability

We have checked that the contents of this document correspond to the hardware and software described. However, deviations cannot be entirely excluded, and we do not guarantee complete conformance. The information contained in this document is, however, reviewed regularly and any necessary changes will be included in the next edition. We welcome suggestions for improvement.

© Siemens AG 2013

Subject to change without prior notice.

s

Copyright © Siemens AG, 2013 What's New In SIMIT V7.1?

Process Automation Page I

Contents

1 GENERAL 1

1.1 New installation of SIMIT 1

1.2 Updating SIMIT 1

1.3 Firmware update 1

2 NEW PRODUCT STRUCTURE 6

2.1 SIMIT STANDARD 6

2.2 SIMIT PROFESSIONAL 6

2.3 SIMIT ULTIMATE 6

3 NEW MODULES FOR SIMIT 7 8

3.1 CONTEC library (conveyor technology) 8

3.2 Shared memory gateway (SHM) 8

3.3 New control for displaying 3D graphics 8

4 NEW FEATURES IN SIMIT 9

4.1 New features in the basic system 9 4.1.1 Approved for Windows 7 64-bit 9 4.1.2 Starting without a dongle in demo mode 9 4.1.3 Starting by double-clicking the .simit file 10 4.1.4 Editing diagrams while a simulation is running 11 4.1.5 Version tracking in the simulation project 12 4.1.6 Read-only attribute 14 4.1.7 Additional formats for the Digital Input and Digital Output controls 15 4.1.8 Correction in the Stepping Switch with Image control 17 4.1.9 New conversion components 17

4.1.9.1 Real2Byte component type 17 4.1.9.2 Byte2Real component type 18

4.1.10 Additional features in "Find and Replace" 19 4.1.10.1 Navigation via the search results 19 4.1.10.2 Updating components by type 20 4.1.10.3 Searching for fixed signals 21

4.1.11 Additional features in the consistency check 21 4.1.11.1 Detection of overlapping gateway signals 21 4.1.11.2 Exporting the results 22

4.1.12 Displaying the absolute address of Simatic signals 22 4.1.13 Displaying the input and output values of components 23 4.1.14 Displaying vectors in the Properties dialog 24 4.1.15 Hotkey for Individual step 25

s


Process Automation Page II

4.1.16 Adjustable timeout times 25 4.1.17 Minimum size for diagrams and templates 25

4.2 New features in the graphics editor (DGE) 26 4.2.1 Flipping graphics 26

4.3 New features in the macro component editor (MCE) 26 4.3.1 New design for the Macros task card 26 4.3.2 Additional properties and know-how protection 28 4.3.3 Using topological connectors in the macro component 29 4.3.4 Default settings for macro component inputs 30 4.3.5 Find and Replace in macro components 31

4.4 New features in the SMD function module 31 4.4.1 Automatic parameter import 31

4.4.1.1 Table format 31 4.4.1.2 Importing the table 32 4.4.1.3 Copying parameter changes made while the simulation is running 34

4.4.2 New SIMIT templates adapted to PCS 7 V8.0 35 4.4.3 Importing files in Excel format 35 4.4.4 Creating tables from a template 36 4.4.5 Selection options in the preview 37 4.4.6 Finding and replacing component types and macros in templates 38 4.4.7 Placeholders for control properties 38 4.4.8 Defining a folder hierarchy for templates 39 4.4.9 Addressing a module via the I/O address 40 4.4.10 Indirect addressing 40 4.4.11 Opening basic templates in the editor 41 4.4.12 Generic import interface 41

4.4.12.1 Import file syntax 41 4.4.12.2 Example: Single template instantiation 46 4.4.12.3 Example: Grouped template instantiation 46 4.4.12.4 Example: Diagram creation 47 4.4.12.5 Importing the XML file 48

4.5 New features in the PLCSIM and PRODAVE gateway 49 4.5.1 Flexible symbol import 49 4.5.2 Transferring scaling 51 4.5.3 Importing PLC variable lists 52

4.6 New features in the PROFIBUS DP and PROFINET IO gateway 53 4.6.1 Flexible symbol import 53 4.6.2 Transferring scaling 53 4.6.3 Importing the configuration file 54 4.6.4 Importing PLC variable lists 55 4.6.5 Support for TIA Portal V11 for transferring the hardware configuration 55

4.7 New features in the PROFINET IO gateway 56 4.7.1 Data record communication 56

s


Process Automation Page III

4.7.2 Plugging and unplugging modules 56 4.7.3 Assigning a MAC start address 57

4.8 New features in the OPC gateway 58 4.8.1 Exporting and importing the signal list 58 4.8.2 Fault correction when restoring a connection 59

4.9 New features in the component type editor (CTE) 59 4.9.1 Starting the editor by double-clicking .simcmp files 59 4.9.2 Opening component types from the task card 59 4.9.3 Controls on the basic and link symbol 59 4.9.4 Animations on the basic and link symbol 59 4.9.5 Flipping graphics 60 4.9.6 New byte data type 60 4.9.7 Free positioning of connectors 60 4.9.8 Scalability of graphics 60 4.9.9 New property: Proportionally scalable only 61 4.9.10 Using vectors with complex connection types in controls 61 4.9.11 Scalability 62 4.9.12 File selection dialog when changing the name or version 63 4.9.13 New _INDEX system variable 63

s


Process Automation Page IV

Table of figures Figure 1-1: SIMBApro toolbar 2 Figure 1-2: Info dialog 2 Figure 1-3: Entering the IP address 3 Figure 1-4: Displaying the current firmware version 3 Figure 1-5: Selecting the update file 4 Figure 1-6: Progress of the firmware update 5 Figure 4-1: Prompt to start in demo mode 9 Figure 4-2: Switching the project navigation 11 Figure 4-3: Version number in the Project Manager 12 Figure 4-4: Version number in the Project Manager with indication of change 12 Figure 4-5: Dialog to increment the project version 12 Figure 4-6: Operating window for the ProjectVersion component type 13 Figure 4-7: Script to output the project version 13 Figure 4-8: Read-only attribute in the Properties dialog of the Project Manager 14 Figure 4-9: Applying the read-only attribute 14 Figure 4-10: Setting the display format 16 Figure 4-11: Effect of different display formats and data widths 17 Figure 4-12: Single precision floating-point number as defined in IEEE 754 18 Figure 4-13: Single precision floating-point number as defined in IEEE 754 18 Figure 4-14: Navigation via the search results 19 Figure 4-15: Updating components 20 Figure 4-16: No hits found in the search 20 Figure 4-17: Find & Replace in the context menu of macro components 20 Figure 4-18: Searching for fixed signals 21 Figure 4-19: Overlapping input signals in the consistency check 21 Figure 4-20: Exporting inconsistencies 22 Figure 4-21: Absolute address displayed in the Properties dialog 22 Figure 4-22: Absolute address displayed in the Signals task card 23 Figure 4-23: Displaying input and output values in the toolbar 23 Figure 4-24: Vector elements displayed in the Properties dialog 24 Figure 4-25: Vector with collapsed elements 24 Figure 4-26: Display of vector elements of complex connectors 25 Figure 4-27: The Macros task card 27 Figure 4-28: Diagnostics in the Properties dialog for macro components 28 Figure 4-29: Properties of a macro component 29 Figure 4-30: Definition of a macro component with topological connectors 30 Figure 4-31: Use of a macro component with topological connectors 30 Figure 4-32: Default settings for macro component inputs 31 Figure 4-33: Context menu for a macro component 31 Figure 4-34: Example of a parameter table 32 Figure 4-35: Calling automatic parameter import 32 Figure 4-36: Import dialog for automatic parameter import 32

s


Process Automation Page V

Figure 4-37: Preview of automatic parameter import 33 Figure 4-38: Diagram before the parameter import 34 Figure 4-39: Diagram after the parameter import 34 Figure 4-40: Reference to available list of changes 35 Figure 4-41: Copying changes from the last simulation 35 Figure 4-42: Exporting a template 36 Figure 4-43: Automatically created import file 37 Figure 4-44: Selection options in the SMD preview 37 Figure 4-45: Context menu for a template 38 Figure 4-46: Use of the Unit connector 40 Figure 4-47: Basic template displayed in the editor 41 Figure 4-48: SMD function in the Project Manager 48 Figure 4-49: Selecting an *.xml file 49 Figure 4-50: Example of gateway signals 50 Figure 4-51: Signals following import with the New option 50 Figure 4-52: Signals following import with the Add option 51 Figure 4-53: Signals following import with the Overwrite option 51 Figure 4-54: Copy cell 52 Figure 4-55: Paste to cell 52 Figure 4-56: Copy cell 53 Figure 4-57: Paste to cell 54 Figure 4-58: Importing the configuration file 55 Figure 4-59: Importing system data from TIA Portal 56 Figure 4-60: Plugging and unplugging modules 57 Figure 4-61: Assigning a MAC start address 57 Figure 4-62: Message indicating invalid MAC start address 58 Figure 4-63: Display of the MAC start address 58 Figure 4-64: Component type with button on the basic symbol 59 Figure 4-65: Position coordinates for a connector 60 Figure 4-66: Settings for scaling graphics on components 61 Figure 4-67: Proportionally scalable only option 61 Figure 4-68: Control with vector element for a complex connection type 62 Figure 4-69: Using the _INDEX system variable 63

s


Process Automation Page VI

List of tables Table 1-1: Firmware update for IM-PBDP 4 Table 1-2: Firmware update for IM-PNIO 4 Table 4-1: Keys for timeout times 25 Table 4-2: Placeholders for controls 39 Table 4-3: Parameter value for the NC/NO contact type 39 Table 4-4: Parameter value for the Off/On default setting 39 Table 4-5: Comparison of data types 52 Table 4-6: Comparison of data types 55 Table 4-7: System variables for determining the component dimensions 63

s General


Process Automation Page 1

1 GENERAL This software comprises SIMIT V7.1. SIMIT V7.1 offers a range of new functions that are described in the sections below.

The SIMIT V7.1 installation files are contained on the SIMIT software CD. This CD is a fully functional installation CD. If you already have SIMIT version 7.0 installed on your computer, you can also use this SIMIT software CD to update this installation.

NOTE For SIMIT V7.1 you need new licence keys.

1.1 New installation of SIMIT

Use the SIMIT software CD if you want to install SIMIT V7.1 for the first time. The installation procedure is described in the installation manual. The manual is available as a pdf file in the docs directory on the SIMIT software CD.

1.2 Updating SIMIT

Please run the SIMITInstaller on the SIMIT software CD to update an existing SIMIT V7.1 installation. Choose Repair/upgrade in the installation dialog.

The update will not affect any of your existing projects.

CAUTION To avoid problems arising from country-specific table delimiters, the import of data files in SIMIT V7.1 has been converted to *.txt format. Data in this format is separated by tabs.

Files may need to be converted to *.txt format.

1.3 Firmware update

You must also update the firmware versions of the Profibus and Profinet interface modules that you want to use with SIMIT V7.1.

s General



STOP

WARNING You must close SIMIT before loading a firmware update to the interface module.

To start the update, run SIMBApro.exe from the SIMBApro subfolder in the SIMIT installation folder. Select Help | Info, as shown in Figure 1-2.

Figure 1-1: SIMBApro toolbar

Select Scan Network in the pop-up dialog (Figure 1-2).

Figure 1-2: Info dialog

Enter the address of your interface module in the IP address field of the dialog and press OK to confirm (Figure 1-3). Do not use the Scan Network function at this point.

s General



Figure 1-3: Entering the IP address

If your interface module can be accessed in the network, the current firmware version is displayed (4.004.4 in this example (Figure 1-4)).

Figure 1-4: Displaying the current firmware version

Click Firmware Update and select the appropriate update file (Figure 1-5).

s General



Figure 1-5: Selecting the update file

Profibus update files can be found in the IM-PBDP subfolder and Profinet update files in the IM-PNIO subfolder in the Hardware folder of the SIMIT CD. Please note that the correct update file as per Table 1-1 and Table 1-2 must be loaded for each type of interface module.

Interface module File name

IM-PBDP-2 simbapb_2.006.05.upd



Table 1-1: Firmware update for IM-PBDP

Interface module File name

IM-PNIO-128/256 simba3.405.7.upd

Table 1-2: Firmware update for IM-PNIO

s General



STOP

WARNING It can take up to 30 minutes to update the firmware. Do not switch off the interface module while the update is in progress.

The progress of the update is displayed, as shown in Figure 1-6.

Figure 1-6: Progress of the firmware update

The interface module must be reset to complete the update. Click OK to reset the interface module.

You can now exit SIMBApro and restart SIMIT, reload the interface module with the project data and if necessary also restart the connected controller.

s New product structure



2 NEW PRODUCT STRUCTURE SIMIT is now offered in three configurations only:

• SIMIT STANDARD

• SIMIT PROFESSIONAL

• SIMIT ULTIMATE

2.1 SIMIT STANDARD

SIMIT STANDARD contains modules as follows:

• Macro Component Editor (MCE) for creating and editing macro components.

• Dynamic Graphics Editor (DGE) for creating and editing graphics on diagrams and for animating graphic objects.

• Trend & Message Editor (TME) for visualizing signal charts and for displaying messages.

• Automatic Control Interface (ACI) for script-based simulation control including an editor to edit scripts.

• Profibus DP-Kopplung for connecting SIMIT to Profibus DP.

• Profinet IO-Kopplung for connecting SIMIT zo Profinet IO.

• PRODAVE-Kopplung for connecting SIMIT to a SIMATIC S7-PLC using the PRODAVE-interface.

As a library the standard library with its component types and controls is included.

2.2 SIMIT PROFESSIONAL

SIMIT PROFESSIONAL contains all features as provided in SIMIT STANDARD and additionally modules as follows:

• Structured Model Diagrams (SMD) for autmatic simulation setup based on tabes and templates including an editor for creating and editing templates.

• PLCSIM-Kopplung for connecting SIMIT to S7-PLCSIM.

• OPC-Kopplung for connecting SIMIT to an OPC DA-Server or to OPC DA-Clients.

2.3 SIMIT ULTIMATE

SIMIT ULTIMATE contains all features as provided in SIMIT PROFESSIONAL and additionally modules as follows:

s New product structure



• Component Type Editor (CTE) for creating your own library components including an editor for creating and editing component types.

• XML-Schnittstelle for simulation setup based in an XML-file.

• Shared Memory-Kopplung for connecting SIMIT to other applications using a shared memory.

s New modules for SIMIT 7



3 NEW MODULES FOR SIMIT 7 SIMIT 7.1 includes a new library, a new gateway and a new control.

3.1 CONTEC library (conveyor technology)

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 in order to simulate the transport of objects in this system. The CONTEC library provides a special solver for this purpose for use in SIMIT. Once the simulation has been started, the solver continuously calculates the positions of the objects in the modelled conveyor system.

Please refer to the user manual for this library for a detailed description.

3.2 Shared memory gateway (SHM)

The shared memory gateway, or SHM gateway for short, can be used to exchange signals from SIMIT with any other application via a shared memory (SHM). This gateway provides a universal, high-performance signal interface to SIMIT.

Please refer to the user manual for this gateway for a detailed description.

3.3 New control for displaying 3D graphics

The 3D Viewer control gives you the option of incorporating three-dimensional animated views of a machine in your simulation. The representation of the machine is then clear, and the movements of the machine are displayed realistically.

Like the other controls in the basic library, the 3D Viewer control is inserted in a diagram and parameterized 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.

Please refer to the basic library reference manual for this control for a detailed description.

s New features in SIMIT



4 NEW FEATURES IN SIMIT SIMIT V7.1 includes a number of new features, which are described in more detail below.

4.1 New features in the basic system

The following new features are now available in the basic system of SIMIT V7.1:

4.1.1 Approved for Windows 7 64-bit

SIMIT is now approved for use with the 64-bit version of the Microsoft Windows 7 operating system.

PLCSIM version 5.4 SP5 is needed to use the PLCSIM gateway with Windows 7.

PRODAVE version 6.2 is needed to use the PRODAVE gateway with Windows 7.

4.1.2 Starting without a dongle in demo mode

If you start SIMIT without plugging a SIMIT dongle into your computer, you are asked whether you want to start SIMIT in demo mode (Figure 4-1).

Figure 4-1: Prompt to start in demo mode

If you have a valid SIMIT licence and therefore a SIMIT dongle, this demo mode does not apply. It is intended purely to give you a feel of what SIMIT can do before you buy a licence.

In demo mode only the following SIMIT function modules are available, regardless of any licence keys you may have:

• SIMIT BASIC, the basic SIMIT system

• the macro component editor (MCE)

• the graphics editor (DGE)

• the message system and graphs (TME)

• template editing and instantiating (SMD)

• scenarios (ACI)




In demo mode SIMIT offers only limited functionality with regard to the following elements:

• Saving and archiving

You can save projects, templates and macro components in demo mode, but you can only use the projects, templates and macro components created in demo mode on the computer on which they were created. In particular, the projects, templates and macro components created in demo mode are not compatible with the full version of SIMIT.

You cannot archive projects in demo mode.

• Opening and dearchiving

In demo mode you can only open projects that have been saved on this computer in demo mode. Projects created in a full version cannot be opened.

You can dearchive projects that have been archived in a full version. But bear in mind that if you change the project in demo mode, it will no longer be able to be used in the full version.

• Address range

The addresses that can be used with the PLCSIM and PRODAVE gateway are limited to the following ranges:

EB0 – EB7 and EB64 – EB85 AB0 – AB7 and AB64 – AB79

• Runtime

You can use SIMIT in demo mode for as long as you want, but the runtime of a simulation is limited to 30 minutes. At the end of the 30 minutes, the simulation will end automatically. You can restart it once it has ended.

• Number of gateways

You can only create one gateway in a SIMIT project in demo mode.

• Project folder

In demo mode you can only store projects in a designated location in the SIMIT working area.

• Libraries for macro components and templates

In demo mode you can only store macro components and templates within the SIMIT working area. You cannot open other library folders.

4.1.3 Starting by double-clicking the .simit file

You can now also start SIMIT by double-clicking the *.simit file in a project folder. The corresponding project is then already open once SIMIT starts.




4.1.4 Editing diagrams while a simulation is running

You can now make changes to the simulation model while a simulation is running. These changes take effect the next time the simulation is started. To make changes while the simulation is running, simply switch between "Simulation" and "Project" in the project navigation (Figure 4-2).

Figure 4-2: Switching the project navigation

You can open diagrams in both views, but for different purposes: • If you are in the blue project tree, diagrams are opened for editing. The changes that

you make take effect the next time the simulation is started. The window title bar is shown in blue.

• If you are in the orange simulation tree, diagrams are opened for use. Their content corresponds to the simulation that is running and cannot be changed. The window title bar is shown in orange.

You can open the same diagram in both modes at the same time. When the simulation ends, the diagram opened from the simulation tree closes automatically.

When the simulation is running, there are some restrictions as to the actions that can be carried out in the project tree:

• You cannot create PROFIBUS DP, PROFINET IO or SIMBA gateways.

• The PROFIBUS DP, PROFINET IO and SIMBA gateways cannot be used for imports, and interface modules cannot be loaded.

• The SMD, CDL and API functions are not available.




4.1.5 Version tracking in the simulation project

The version number is now automatically included in the simulation project. It consists of several elements:

• Licence number (e.g. AB12345)

• Time stamp (resolution is approx. 38 seconds)

• Major version (0-127)

• Minor version (0-999)

If the simulation project is changed, the version number is updated automatically the next time the simulation is started. The version number is displayed in the Project Manager (Figure 4-3).

Figure 4-3: Version number in the Project Manager

If the simulation project has been changed but has not been started since then, an asterisk appears after the version number (Figure 4-4).

Figure 4-4: Version number in the Project Manager with indication of change

The minor version is incremented up to 999, then it returns to zero and the major version is increased by 1. If you want to increment the major version before then, to document a particular project status for example, click the button with the three dots. After a prompt (Figure 4-5), the project is compiled and the new version number entered.

Figure 4-5: Dialog to increment the project version

The project version can also be determined using the ProjectVersion component type. This component type is located in the standard library in the Misc subfolder. It has the following symbol:




At the outputs of a component of this type the following integer values are available:

• ProjectVersion The complete version number coded in numerical form.

• LicenseNumber The licence number coded in numerical form.

• TimeStamp The time stamp.

• MajorVersion The major version.

• MinorVersion The minor version.

The individual version numbers are displayed in readable form in the component's operating window (Figure 4-6).

Figure 4-6: Operating window for the ProjectVersion component type

If the ACI (Automatic Control Interface) module is being used, the project version can be accessed via the _ProjectVersion system variable. This allows the project version to be output in the log file, for example, as shown in Figure 4-7.

Figure 4-7: Script to output the project version




4.1.6 Read-only attribute

In SIMIT it is now possible to protect entire simulation projects or parts of them against accidental changes. All protectable elements of a project now have an additional "Read-only" attribute in the Project Manager (Figure 4-8).

Figure 4-8: Read-only attribute in the Properties dialog of the Project Manager

When you set or remove the read-only attribute for a folder, you can choose to apply this action recursively to all subfolders and the elements they contain. Note that the read-only attribute for individual objects such as diagrams in lower-level folders can still be changed subsequently on an individual basis, so it is not permanently tied to the folder status.

Figure 4-9: Applying the read-only attribute

The effect of the read-only attribute varies according to which element of a project it is applied to:

• Diagram Read-only diagrams cannot be deleted or renamed. They can be opened in the editor but not modified. Diagram objects (components, controls and graphics) can be selected and copied to other diagrams. Diagrams can be opened while the simulation is running.

• Diagram folders Read-only folders cannot be deleted or renamed. New diagrams or subfolders cannot be created in read-only folders, not even by moving or copying diagrams or folders.

• Gateways Read-only gateways cannot be deleted or renamed. They can be opened in the editor but not modified.

• Snapshots Read-only snapshots can be loaded when a simulation is running but not deleted or renamed.




• Snapshot folders Read-only folders cannot be deleted or renamed. Subfolders or snapshots cannot be created in read-only folders, not even by moving or copying snapshots or folders. If the highest-order snapshot folder in the project tree is set to read-only, no more snapshots can be created as they are automatically stored in the highest-order snapshot folder. The corresponding icon in the toolbar is inactive.

• Graph Read-only graphs cannot be deleted or renamed. They can be opened in the editor but not modified.

• Archive A read-only archive can be opened in the editor but not modified.

• Script Read-only scripts cannot be deleted or renamed. They can be opened in the editor but not modified.

• Script folders Read-only folders cannot be deleted or renamed. New scripts or subfolders cannot be created in read-only folders, not even by moving or copying scripts or folders.

• Project Manager If the Project Manager is set to read-only, project properties such as cycle times cannot be modified. However, all actions relating to project elements are available in both the Project Manager and the project tree, subject to any read-only settings.

• Complete project Read-only projects cannot be renamed and gateways cannot be created.

Note that setting the read-only attribute for a project does not automatically mean that all components of the project are protected from being changed. However, when you set the read-only attribute for a project, you can pass it on to all elements of the project.

Read-only elements such as diagrams are opened in the editor with a white title bar to indicate their special status.

4.1.7 Additional formats for the Digital Input and Digital Output controls

The Digital Input and Digital Output controls can now output integer values as decimal numbers, hexadecimal numbers or ASCII characters.




Figure 4-10: Setting the display format

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 The data width setting is also relevant for the display of decimal numbers. If the data width is set to less than 8, the actual value of an integer input variable may not be displayed in some circumstances.

If you enter values using the Digital Input control, you must use the specified display format. If the syntax used does not correspond to the specified display format, the input is interpreted as zero.

The data width does not affect the input of a value as the effective value is not limited. However, the way the value is displayed will depend on the data width setting.

Figure 4-11 shows examples of the effect of different display formats and data widths.




Figure 4-11: Effect of different display formats and data widths

4.1.8 Correction in the Stepping Switch with Image control

In the "Up-Down" parameter setting the value of the Stepping Switch with Image is now incremented when you click in the top half of the control and decremented when you click in the bottom half.

4.1.9 New conversion components

Two new component types are available for converting REAL values.

4.1.9.1 Real2Byte component type Symbol

Function The Real2Byte component type converts the value of an analog signal at the REAL input into the binary representation of a single precision floating-point number as defined in IEEE 754. The converted floating-point number is mapped to the four byte values Bi, i = 0, ... ,3, at the integer outputs, as shown in Figure 4-12.




Figure 4-12: Single precision floating-point number as defined in IEEE 754

NOTE Mapping the analog signal (double precision type) to the single precision number format limits the precision and the value range.

Note also that this conversion cannot be used to convert a floating-point number to a whole number (integer). The Analog2Integer component type should be used for that conversion.

If you want to transfer analog signals to a Simatic controller, you normally set the data type of the corresponding signal in the gateway 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.

4.1.9.2 Byte2Real component type Symbol

Function The Byte2Real component type converts the binary representation of a single precision floating-point number 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 Figure 4-13.

Figure 4-13: Single precision floating-point number as defined in IEEE 754




NOTE Note that this conversion cannot be used to convert a whole number (integer) to a floating-point number. The Analog2Integer component type should be used for that 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 gateway 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.

4.1.10 Additional features in "Find and Replace"

4.1.10.1 Navigation via the search results If a search result can be matched to a specific diagram, you can now open the corresponding diagram by double-clicking the search result. As before, however, you can still also select the search result and then double-click the diagram in the Project Elements area.

If there are several project elements corresponding to a search result, you still need to double-click the desired project element to open it (see Figure 4-14).

Figure 4-14: Navigation via the search results




4.1.10.2 Updating components by type When replacing components by type, you can update components in your simulation project using the Update option (see Figure 4-15). If you choose this alternative, the system searches by component type for all components in the defined search area that have the same name and belong to the same library family but were created (saved) at a later date. The search for current component types takes place in all component libraries of the Components task card, in the following order of palettes: 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.

Figure 4-15: Updating components

The Update option works in the same way for all macro components contained in the defined search area, with the search for current macro components taking place in the libraries of the Macros task card. If all components and macro components in the chosen search area are already up to date, the message dialog shown in Figure 4-16 is displayed as the result.

Figure 4-16: No hits found in the search

The Update option is also available if you want to update components by type in macro components. Start the update via the context menu for the macro component (Figure 4-17).

Figure 4-17: Find & Replace in the context menu of macro components




4.1.10.3 Searching for fixed signals You can now search specifically for fixed signals in the simulation project. In the search for signals dialog activate the search option Fixed signals only (see Figure 4-18). In this way you can get an overview at any time of which signals are currently fixed.

Figure 4-18: Searching for fixed signals

As signals can only be fixed when the simulation is running, this search option is only available once the simulation is running.

4.1.11 Additional features in the consistency check

4.1.11.1 Detection of overlapping gateway signals The consistency check has been extended to allow overlapping input signals in gateways to be detected. Two signals overlap if they access part or all of the same address range. For example, signals E0.4 and EB0 overlap because E0.4 is within the address range of EB0. The consistency check shows these overlapping signals as inconsistencies, as shown in Figure 4-19.

Figure 4-19: Overlapping input signals in the consistency check

In the shared memory gateway (SHM gateway) the input and output signals are mapped to a shared memory. For that reason no overlaps between input and output signals are permissible for this gateway. Overlapping input and output signals are detected in the consistency check for this gateway and displayed as inconsistencies.




4.1.11.2 Exporting the results The results of the consistency check can now also be exported in a tab-separated text file. To do so, activate the button in the consistency check editor as shown in Figure 4-20.

Figure 4-20: Exporting inconsistencies

4.1.12 Displaying the absolute address of Simatic signals

The signals in Simatic gateways, i.e. in the PROFIBUS DP, PROFINET IO, PLCSIM and PRODAVE gateways, are addressed via symbolic names where they have been defined. The absolute address is now displayed both in the properties of the input and output connectors (Figure 4-21) and in the Signals task card (Figure 4-22).

Figure 4-21: Absolute address displayed in the Properties dialog




Figure 4-22: Absolute address displayed in the Signals task card

4.1.13 Displaying the input and output values of components

When the simulation is running, the display of current input and output values of components can be switched on in the Properties dialog of the component by means of the button. To switch on the display of all inputs and outputs of components on a diagram at the click of a mouse, you can now use the same command in the diagram's toolbar (see Figure 4-23).

Figure 4-23: Displaying input and output values in the toolbar

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 diagram.




4.1.14 Displaying vectors in the Properties dialog

Vectors of inputs and outputs, parameters and states are now grouped together in the Properties dialog and displayed in the numerically correct order, as shown by way of example in Figure 4-24.

Figure 4-24: Vector elements displayed in the Properties dialog

The vector elements can be expanded and collapsed. Figure 4-25 shows a vector with collapsed elements.

Figure 4-25: Vector with collapsed elements

For connectors with complex connection types an additional expandable and collapsible level has been added (Figure 4-26).




Figure 4-26: Display of vector elements of complex connectors

4.1.15 Hotkey for Individual step

The Individual step function has now been assigned to function key F12. It works in exactly the same way as the Simulation | Individual step menu item.

4.1.16 Adjustable timeout times

Various operations are monitored by SIMIT and terminated if they overrun a predefined time, in order to maintain SIMIT's operability.

These timeout times are set so that as a general rule they are not exceeded. If, however, you receive a message that a timeout has been exceeded, please check first to see whether it is due to a SIMIT error. If not, you can increase the timeout times in the Windows Registry. The corresponding keys are located under "HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SIMIT7\SIMIT".

Name Default setting [ms] Minimum value [ms]timeout1 4000 4000

timeout2 10000 10000

timeout3 60000 60000

Table 4-1: Keys for timeout times

4.1.17 Minimum size for diagrams and templates

The minimum size for diagrams and templates has been reduced to 20 x 20 pixels.




4.2 New features in the graphics editor (DGE)

4.2.1 Flipping graphics

Graphics can now be flipped horizontally and vertically using the corresponding icons ( , ) in the graphics editor toolbar.

4.3 New features in the macro component editor (MCE)

4.3.1 New design for the Macros task card

The Macros task card has been redesigned to bring it into line with the Components task card (Figure 4-27). Therefore the Macros task card is now divided into the Basic macros, User macros and Project macros palettes. The name, version, library and UID of a selected macro component are displayed under Info.




Figure 4-27: The Macros task card

You can create your own macro components in either the User macros or the Project macros palette. Macro components created in the User macros palette are stored in the SIMIT working area and are therefore available for all projects. In User macros you can also open folders containing macro components using the button. The button closes a selected folder, i.e. removes it from the palette again.

Macro components created in the Project macros palette are stored in the project folder and are therefore only available while this project is open. All macro components stored in Project macros are archived with the project. Therefore they are available in the project again if you dearchive the project.

Macro components containing errors are identified by means of the overlay. You can open and edit these macro components in the editor, but you cannot use them on diagrams. You will find a description of the errors in the editor's Properties dialog on the Diagnostics tab (Figure 4-28).




Figure 4-28: Diagnostics in the Properties dialog for macro components

The section Basic Macros contains five macros which may be used as signal generators. They can be parametrized with respect to cycle duration and amplitude and yield different signal patterns:

• Random,

• Sawtooth,

• Sine,

• Square, and

• Triangle.

4.3.2 Additional properties and know-how protection

Macro components now have some additional properties, which you can edit in the Properties dialog (Figure 4-29):

Name

The name of a macro component corresponds to the file name under which a macro component is saved in the file system (working area or any directory in the file system). The macro component is displayed with this name in the Macros task card.

If macros have been copied over from an earlier SIMIT version, the file name may differ from the macro name to begin with.)

Abbreveation The abbreveation is displayed in the header in the instance of a macro component.

Version

The version of a macro component can be freely assigned. It appears in the Info palette in the Macros task card and in the tooltip for the macro component on the diagram.

Library family

The library family of a macro component can be freely assigned. It appears in the Info palette in the Macros task card and in the tooltip for the macro component on the diagram.

Password

Macro components can be password protected. If a macro component is password protected, it can be used on diagrams but cannot be opened without entering the correct password.




STOP

WARNING 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.

Figure 4-29: Properties of a macro component

4.3.3 Using topological connectors in the macro component

You can now use components from the FLOWNET and CONTEC supplementary libraries in macro components. Open topological connectors of a model created from FLOWNET or CONTEC components are mapped to topological connectors in the margin bars of the macro component. The topological connectors can be arranged on the right or left margin of the macro component as preferred (Figure 4-30).




Figure 4-30: Definition of a macro component with topological connectors

If macro components like this are used on diagrams, the topological connectors of the macro component (Figure 4-31) can be connected to topological connectors of other components or macro components. The topological structures defined in the macro components are then merely substructures of the complete topological structure of the flow or transport network.

Figure 4-31: Use of a macro component with topological connectors

4.3.4 Default settings for macro component inputs

Default settings can be applied to individual macro component inputs. Open the Input tab in the Properties dialog of the macro component editor and enter the corresponding values (Figure 4-32).




Figure 4-32: Default settings for macro component inputs

4.3.5 Find and Replace in macro components

In SIMIT V7.1 you can now also replace components within a macro. The context menu for a macro includes the item Find & Replace.

Figure 4-33: Context menu for a macro component

4.4 New features in the SMD function module

4.4.1 Automatic parameter import

Using automatic parameter import (API) you can automatically copy values for the following variables from tables and insert them in existing diagrams:

• Parameters (apart from parameters of the "dimension", "characteristic" and "text" type)

• Default input settings

• Default control settings (corresponds to input X of the control)

4.4.1.1 Table format The table for automatic parameter import must have three columns as follows:

• The first column contains the name of the component to be modified

• The second column contains the name of the connector or parameter, and

• The third column contains the value to be copied

Each row of the table describes the substitution for a parameter. Figure 4-34 shows an example of a table opened in Excel.




Figure 4-34: Example of a parameter table

4.4.1.2 Importing the table The API function is activated by means of the icon in the Project Manager toolbar (Figure 4-35).

Figure 4-35: Calling automatic parameter import

In the import dialog (Figure 4-36) that opens, select the file corresponding to the table you wish to import. You can also specify which variables (parameters, inputs, controls) are to be copied from the table. You can import an Excel file in *.xls or *.xlsx format or a tab-separated text file.

Figure 4-36: Import dialog for automatic parameter import

In the import dialog preview (Figure 4-37) you can see which substitutions are to be made for the parameter table from Figure 4-34.




Figure 4-37: Preview of automatic parameter import

Figure 4-38 shows the original diagram, while the changes resulting from automatic parameter import are shown in Figure 4-39.




Figure 4-38: Diagram before the parameter import

Figure 4-39: Diagram after the parameter import

NOTE If you want to set enumeration type parameters, please enter a numerical value specifying the desired position of the term within the enumeration. The numbers start at 0.

4.4.1.3 Copying parameter changes made while the simulation is running Automatic parameter import also lets you copy parameter changes that were made while the simulation was running to the simulation project once the simulation has ended. During the simulation SIMIT records which default input settings and parameters are changed and which controls are used. Once the simulation has ended the latest settings are made available as a list and can be copied to the simulation project by automatic parameter import.




When the simulation ends a corresponding message is displayed (Figure 4-40). If you do not need to see this message again, you can choose for it not to be displayed in future.

Figure 4-40: Reference to available list of changes

Each time the simulation is run, the list of changes is automatically stored in the SIMIT working area. If you select the Copy changes from the last simulation option in the import dialog (Figure 4-41), the corresponding file is selected.

Figure 4-41: Copying changes from the last simulation

4.4.2 New SIMIT templates adapted to PCS 7 V8.0

SIMIT V7.1 comes with templates adapted to PCS 7 V8.0. They are located in the template folder PCS 7 AP Library V80.

4.4.3 Importing files in Excel format

The following table formats are now supported for import:

• *.iea The table format used by the Import/Export wizards in PCS7




• *.xls Microsoft Office Excel (97-2003) format. Only the first sheet of the workbook is included. This file format is only available if Microsoft Excel is installed on your computer.

• *.xlsx The current Microsoft Excel format. Only the first sheet of the workbook is included.This file format is available even if Microsoft Excel is not installed on your computer.

• *.txt Tab-separated list in text format.

NOTE If you still want to use *.csv files from projects in earlier versions of SIMIT, you must convert them to this tab-separated *.txt format.

4.4.4 Creating tables from a template

If you want to create a table for a template so as to then instantiate the template repeatedly, SIMIT now allows you to create a table with a title row matching the template. In the context menu for the template select Export to Excel.

Figure 4-42: Exporting a template

The next steps will depend on whether or not Microsoft Excel is installed on your computer.

• Microsoft Excel installed A new workbook is 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 the SMD 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 at a later date – possibly on another computer.




The first three columns of the table 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 data yourself.

Figure 4-43: Automatically created import file

NOTE Please note that when this table is imported, the profile is set to Placeholders defined in the first row.

4.4.5 Selection options in the preview

In the SMD preview you can now decide whether to copy all information from the table or whether to deselect certain substitutions.

Figure 4-44: Selection options in the SMD preview




If a diagram is deselected in the left-hand tree view, it is not instantiated. By selecting a folder you can also select or deselect multiple diagrams within it. You can tell from the checkbox whether a diagram or folder is selected ( ) or deselected ( ) or whether at least one checkbox in one of the lower-order folders is deselected ( ).

In the right-hand table you can also select and deselect individual substitutions. Deselecting a substitution has the same effect as if the substitution were not present in the table.

4.4.6 Finding and replacing component types and macros in templates

In SIMIT V7.1 you can now also replace components and macros within a template. The context menu for a template includes the item Find & Replace.

Figure 4-45: Context menu for a template

4.4.7 Placeholders for control properties

Previously you could only define the name, time slice and connector of controls as placeholders. Now for some controls you can also define the type, default setting and scaling as placeholders. The list in Table 4-2 shows which properties can be used as placeholders for controls.




Control Name Time slice Type Default setting

Scaling Connector

Button X X X

Button with image X X X

Switch X X X X

Switch with image X X X X

Stepping switch X X X

Stepping switch with image

X X X

Digital input X X X

Slider X X X X X

Bar indicator X X X X

Binary indicator X X X

Analog display X X X

Digital display X X X

Table 4-2: Placeholders for controls

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 for substitution (see Table 4-3 and Table 4-4).

Type Value

NC contact 0

NO contact 1

Table 4-3: Parameter value for the NC/NO contact type

Default setting Value

Off 0

On 1

Table 4-4: Parameter value for the Off/On default setting

4.4.8 Defining a folder hierarchy for templates

In your tables you can now specify which folder is to be searched for a template. For the TEMPLATE placeholder enter the complete folder hierarchy as shown in the Templates task card. Use the backslash '\' as the separator. To refer to a template that is not located in a subfolder, simply 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 of this name as before. In this case make sure that there are not two templates




with the same name in different subfolders. In principle the three palettes of the Templates task card are searched in the following order:

1. Project templates

2. User templates

3. Basic templates

4.4.9 Addressing a module via the I/O address

The identify of a module on Profibus or Profinet is determined by the slave or device number and the slot number. Accordingly, both values must be entered in the Unit connector if it is used to identify a device, such as a SIWAREX-U balance for example (Figure 4-46).

Figure 4-46: Use of the Unit connector

If devices like this are used on templates, this information is not always available. Instead the module's initial address may be known. Therefore it is now permissible to identify a module on templates by its initial address, for example "EW512" or "AW512" instead of "Dev4:Slt4".

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, an initial address is automatically converted to the address with the slave or device number and slot number. If no gateway with the appropriate address exists when the template is instantiated, the automatic conversion can also be carried out later by means of the Extra | Assign Gateway Signals command.

4.4.10 Indirect addressing

In the Input and Output connectors an additional item of information can now be included on templates, which allows access to signals located relative to a known address. This expression has the form [$+n:RW], where

n is the offset to be added in bytes, R denotes an input or output, i.e. E, I, A or Q, and W denotes the data width, i.e. B, W or D.

So, for example, if the address of a control word EW560 is known, the associated state word AW560 can be specified as follows:

IW560[$+0:QW]

Or, if the control word EW560 has the symbolic name STW1 in the gateway, it can also be specified in the form

STW1[$+0:QW]

If the gateway already exists when the templates are instantiated, an attempt is made to replace the expression with the corresponding signal. If not, this expression is retained even after the signal to which it relates is replaced. For example, if the control word STW1 exists in a PLCSIM gateway with its address IW560 but no associated state word, then the connector




is replaced as follows:

However, you can also start the complete replacement subsequently at any time by calling the Extra | Assign Gateway Signals function.

NOTE Indirect addressing is only supported by the following gateways: PROFIBUS DP, PROFINET IO, PRODAVE, PLCSIM and SIMBA.

4.4.11 Opening basic templates in the editor

Templates in the Basic palette can now be opened directly via the context menu in the template editor. However, basic templates opened in this way can only be viewed, not edited. To indicate this the template is opened in the editor with a white title bar (Figure 4-47).

Figure 4-47: Basic template displayed in the editor

If you wish to edit a basic template, copy it to the User templates palette.

4.4.12 Generic import interface

SIMIT now offers another option for creating diagrams automatically via external files. This can be used to instantiate existing templates but also to create custom diagrams.

4.4.12.1 Import file syntax The file for import must be provided as a text file in XML format and must correspond to the following Document Type Definition:




]>

This definition can be found in the Generic.dtd file in the DTD folder on your SIMIT installation CD.

A valid XML file starts with the element GENERIC. The version number 7.1 should be entered as the attribute for this element.

Element Attribute Description

GENERIC Folder

VERSION In the document form described here, "7.1" must be entered as the version.

The generic import interface can also be used to create a nested folder hierarchy. When you call the SMD function you must select a folder in the Project Manager, in which the folder




hierarchy specified in the import file is then created. If the import file contains no FOLDER elements, the templates are created directly in the selected folder.


FOLDER Generic import interface

NAME The name of a folder to be created. A deeper folder hierarchy can be achieved by nesting several FOLDER tags.

You can choose to instantiate individual templates (TEMPLATE) or combine several templates in a diagram (BUILDUP). In the template enter the name of the template (NAME) and the name of the diagram to be created (INSTANCE) as attributes.


TEMPLATE Template

NAME Template name

INSTANCE Name of the diagram to be created

If you want to combine several templates to create a single diagram, the template elements must be enclosed by a BUILDUP element. In this case the name of the diagram to be created should be entered in the BUILDUP element and not in each individual template element:


BUILDUP Grouped templates

INSTANCE Name of the diagram to be created

ALIGNMENT HOR: Horizontal alignment (side by side) VER: Vertical alignment (one below the other)

WIDTH Maximum width of the diagram in pixels (for horizontal alignment)

HEIGHT Maximum height of the diagram in pixels (for vertical alignment)

Within a template element any number of substitutions for placeholders can be specified using the SUBST element.


SUBST Substitution

NAME Name of the placeholder

VALUE Value to be replaced

Diagrams can also be created without using templates by means of the DIAGRAM element.





DIAGRAM Diagram

NAME Name of the diagram to be created

WIDTH Width of the diagram to be created in pixels

HEIGHT Height of the diagram to be created in pixels

Components on a diagram are described with the COMP element:

c Attribute Description

COMP Component

UID The unique identifier of the component type

NAME The instance name of the component

REF A freely selectable reference name for the component

CYCLE The time slice to which this component is to be assigned (1 to 8).

The component type is identified by means of the unique UID. In order for the component type to be instantiated, it must be present in a library, i.e. in the Components task card.

You also need to specify the name (NAME) to be given to the component on the diagram. If this name already exists when it is imported into the project, SIMIT automatically adds a sequential number to make it unique.

A reference name (REF) only needs to be specified if the name of the component is not unique within the import file and a connection to this component needs 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 value of 2 is entered.

The position of a component is specified by the POS element and its attributes X and Y. The top left corner of the component is specified. The diagram's zero point is in the top left corner of the diagram. Positions must be positive and must be located within the dimensions of the diagram:


POS Position

X The X-position of the component in pixels

Y The Y-position of the component in pixels

A component can also be scaled and rotated with the TRANSFORM element:





TRANSFORM Transformation (scaling, rotation)

SCALEX Scaling in the X-direction (default: 1).

SCALEY Scaling in the Y-direction (default: 1).

ROTATION Angle of rotation in degrees by which the component is to be rotated anticlockwise. The centre of rotation is the component's geometric centre.

A component's parameters can be specified by means of the PROP element and its NAME and VALUE attributes:


PROP Parameter

NAME Parameter name

VALUE Parameter value

Component connectors can be joined together. In some cases this takes place automatically if they are superimposed on the diagram 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 connector using the PORT element:


PORT Component connector

NAME Connector name

The connection is then described by the CONNECTION element:


CONNECTION

Connection

TYPE LINE: Connection to signal line IMPLICIT: Implicit connection

SOURCE The name of the component with which a connection is to be established. If the component has the REF attribute, that value must be used here.

NAME The name of the connector with which the connection is to be established.

The connection of directional signals should always be defined starting from the input, as the input can only be connected to 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 gateway to be connected. Correspondingly, the NAME attribute contains the name of the connector or signal. In the case of connections of the IMPLICIT TYPE the name of the component must be entered in the SOURCE attribute. Reference names (REF) are not permitted here for implicit connections.

Default connector settings are defined by means of the DEFAULT element and its NAME and VALUE attributes.


DEFAULT Default

NAME Connector name

VALUE Default

If no default settings are specified, then the values defined in the component type apply for the connectors.

In accordance with XML conventions, comments are also permitted in the import file:

By way of example the next three sections illustrate diagrams generated from an XML file.

4.4.12.2 Example: Single template instantiation XML file:

Diagram:

4.4.12.3 Example: Grouped template instantiation XML file:




Diagram:

4.4.12.4 Example: Diagram creation XML file:




Diagram:

4.4.12.5 Importing the XML file A valid *.xml file can be imported using the SMD function (Figure 4-48) in the Project Manager.

Figure 4-48: SMD function in the Project Manager

NOTE If you want to check that your data is syntactically correct you can validate your XML using suitable tools before you import it into SIMIT.

In the import dialog simply select the *.xml file to be imported (Figure 4-49).




Figure 4-49: Selecting an *.xml file

CAUTION Please note that when templates are instantiated using an XML file, elements of the template for which no placeholder substitutions have been defined are deleted in the instance.

4.5 New features in the PLCSIM and PRODAVE gateway

4.5.1 Flexible symbol import

When you import a symbol table you can now specify how any existing signals in the gateway are to be handled. There are three options:

• New All existing signals in the gateway are deleted and the gateway is reconstructed using the imported symbol table.

• Add Signals for which a symbol name is specified in the symbol table to be imported but for which no symbol name has been specified yet in the gateway are given the




symbol name specified in the symbol table. However, existing symbol names in the gateway are not overwritten.

If a signal in the symbol table to be imported conflicts with existing signals in the gateway because it covers the same address range, it is ignored. No merging or separation of signals occurs. A signal is only added to the gateway's existing signal set if it does not overlap with existing signals.

• Overwrite Signals for which a symbol name is specified in the symbol table and which are present in the gateway are given this symbol name, regardless of whether a symbol name already exists in the gateway.

If a signal in the symbol table to be imported conflicts with existing signals in the gateway because it covers the same address range, the signal from the symbol table to be imported is used and all conflicting signals are deleted from the gateway.

This procedure can be illustrated by means of a gateway with signals as shown in Figure 4-50.

Figure 4-50: Example of gateway signals

The symbol table to be imported contains the following signals: Symbol_I0.0 I0.0

Symbol_I0.1 I0.1

Symbol_I10.0 I10.0

Symbol_IW2 IW2

Symbol_IW14 IW14

The import of the symbol table leads to different results, depending on the chosen option. Figure 4-51 shows the gateway following an import with the New option.

Figure 4-51: Signals following import with the New option




The result of the import with the Add option is shown in Figure 4-52. Signals IW2 and I10.0 have not been added as they overlap with the existing signals IB2 and IW10.

Figure 4-52: Signals following import with the Add option

Figure 4-53 shows the results following import with the Overwrite option. Signals IB2 and IW10 have now been removed because they have been replaced by the overlapping signals IW2 and I10.0.

Figure 4-53: Signals following import with the Overwrite option

NOTE Unlike input signals, output signals are allowed to overlap in the PLCSIM and PRODAVE coupling. When a symbol table is imported, however, signal overlaps are treated in the same way regardless of whether they are input or output signals.

4.5.2 Transferring scaling

It is now easy to transfer scaling from one signal to another or to a selection of signals. Select the cell you want to copy and then choose the Copy cell item in the context menu (Figure 4-54).




Figure 4-54: Copy cell

You can then select one or more target signals and choose Paste to cell in the context menu for the selection (Figure 4-55).

Figure 4-55: Paste to cell

The scaling type and the lower and upper value can be transferred in this way. This information has to be transferred column by column, however. In addition, you can only paste to cells that are enabled for editing. So for example if the lower and upper values are not editable because no scaling has been set, you need to set the scaling type first or transfer it from an existing signal. Only then can you transfer the associated values.

4.5.3 Importing PLC variable lists

You can now also import PLC variable lists (symbol tables) from the TIA portal. These lists are exported from the TIA portal in EXCEL format (*.xlsx). Only I/O signals with the data types listed in Table 4-5 are copied from the variable list:

TIA portal Step 7 SIMIT

Bool BOOL binary

Byte BYTE integer Word WORD integer Int INT integer DWord DWOR integer DInt DINT integer

Real REAL analog

Table 4-5: Comparison of data types




4.6 New features in the PROFIBUS DP and PROFINET IO gateway

4.6.1 Flexible symbol import

When you import a symbol table you can now specify how any existing signals in the gateway are to be handled. There are three options:

• New All existing signals in the gateway are deleted and the gateway is reconstructed using the imported symbol table. Signals are merged or split if necessary in order to match the data type in the symbol table.

• Add Signals for which a symbol name is specified in the symbol table to be imported but for which no symbol name has been specified yet in the gateway are given the symbol name specified in the symbol table. However, existing symbol names in the gateway are not overwritten.

If a signal in the symbol table to be imported conflicts with existing signals in the gateway because it covers the same address range, it is ignored. No merging or separation of signals occurs.

• Overwrite Signals for which a symbol name is specified in the symbol table and which are present in the gateway are given this symbol name, regardless of whether a symbol name already exists in the gateway.

If a signal in the symbol table to be imported conflicts with existing signals in the gateway because it covers the same address range, the gateway signals affected are merged or split in order to match the data type in the symbol table and assume its symbol name.

4.6.2 Transferring scaling

It is now easy to transfer scaling from one signal to another or to a selection of signals. Select the cell you want to copy and then choose the Copy cell item in the context menu (Figure 4-56).

Figure 4-56: Copy cell

You can then select one or more target signals and choose Paste to cell in the context menu for the selection (Figure 4-57).




Figure 4-57: Paste to cell

The scaling type and the lower and upper value can be transferred in this way. This information has to be transferred column by column, however. In addition, you can only paste to cells that are enabled for editing. So for example if the lower and upper values are not editable because no scaling has been set, you need to set the scaling type first or transfer it from an existing signal. Only then can you transfer the associated values.

4.6.3 Importing the configuration file

Generally speaking, all information that is needed for configuring the interface module can be obtained from the system data blocks. The configuration file is only necessary in addition, in order to configure all signals for a module correctly, if your hardware configuration includes one of the following HART modules in an ET200M station:

6ES7 331-7TF00-0AB0 AI8x16Bit HART/TC

6ES7 331-7TF01-0AB0 AI8x16Bit HART/TC

6ES7 331-7PF00-0AB0 AI8x16Bit HART/TC




6ES7 331-7SF00-0AB0 AI8x16Bit HART/TC

The configuration file can be obtained in the Step 7 hardware configurator (HWConfig) by exporting to *.cfg format. In the import dialog Figure 4-58 you can select the configuration file you require.




Figure 4-58: Importing the configuration file

4.6.4 Importing PLC variable lists

You can now also import PLC variable lists (symbol tables) from the TIA portal. These lists are exported from the TIA portal in EXCEL format (*.xlsx). Only I/O signals with the data types listed in Table 4-5 are copied from the variable list:

TIA portal Step 7 SIMIT

Bool BOOL binary

Byte BYTE integer Word WORD integer Int INT integer DWord DWOR integer DInt DINT integer

Real REAL analog

Table 4-6: Comparison of data types

4.6.5 Support for TIA Portal V11 for transferring the hardware configuration

You may also import a hardware configuration from the TIA portal v11. If you have modeled a SIMATIC S7-300 or S7-400, the configuration will be read from system data blocks (.sdb files), in case of a S7-1200 an .xml file is used.

For TIA portal to provide necessary data, on the machine TIA portal is installed on you need either to install SIMIT V7.1 or launch UnlockHWConfig.exe once. You find this tool on the SIMIT installation CD in the Tools folder.

TIA portal will then place configuration files in the folder \TIAExport.




In order to import system data of a S7-1200 choose “System data (*.xml)” as file type in the file dialog Figure 4-59.

Figure 4-59: Importing system data from TIA Portal

When importing the hardware configuration of a SIMATIC S7-1200, there is no preview available. Therefore, it is not possible to exclude individual slaves or devices from the simulation during import.

4.7 New features in the PROFINET IO gateway

4.7.1 Data record communication

Data record communication is now possible in principle in the PROFINET IO gateway. This type of communication is used for components of type ASM475 and RF170C.

4.7.2 Plugging and unplugging modules

You can now plug and unplug modules in the PROFINET IO gateway too. The corresponding option can be set in the module properties (Figure 4-60).




Figure 4-60: Plugging and unplugging modules

4.7.3 Assigning a MAC start address

All Profinet devices modeled in SIMIT are assigned their own MAC address during import of system data. This MAC address starts with the MAC start address, which has a default of 08:00:06:9D:37:3F (s. Figure 4-61).

In case you are using a single Profinet interface modules only you may leave this setting unchanged. In case you are using several interface modules that are located in the same subnet, the simulated devices must not be assigned the same MAC addresses. In this case please provide different MAC start addresses for different Profinet gateways within a project when importing system data. MAC addresses reserved for simulation are located in the range from 08:00:06:9D:37:3F to 08:00:06:9D:38:3F.

Figure 4-61: Assigning a MAC start address

You may assign arbitrary MAC addresses. Please note however, that when exceeding the range as mentioned above there may be address conflicts arising with other network participants! This is why you are required to confirm those MAC addresses in this case (Figure 4-62).




Figure 4-62: Message indicating invalid MAC start address

CAUTION SIMIT checks only whether the MAC start address lies within the reserved range. SIMIT does not check whether all devices that are imported beginning at the specified start address lie within the reserved range.

The gateway is assigned the MAC start address as chosen during import, this address is displayed in the properties view (Figure 4-63). This start address will be used as default for a new import.

Figure 4-63: Display of the MAC start address

4.8 New features in the OPC gateway

4.8.1 Exporting and importing the signal list

When signals for OPC gateways are exported and imported in *.ini format, all information in the table is now recorded, including default settings and comments for the signals. The signal name, comment and default setting are shown in quotation marks and are separated by semicolons.

If a row contains only the signal name without quotation marks, it is copied as before without a comment and with the standard default setting.




4.8.2 Fault correction when restoring a connection

In case a simulation is running that contains a OPC client gateway, then is stopped, newly initialized and started again, there could be problems arising when connecting to the OPC server which yielded output signals not to be updated any more.

This occurred especially in the case when a snapshot was loaded into a running simulation, since this exact sequence was executed in background.

This issue is resolved with Version V7.1.

4.9 New features in the component type editor (CTE)

4.9.1 Starting the editor by double-clicking .simcmp files

You can now also start the component type editor by double-clicking a component type file (*.simcmp file). Once the component type editor has been started, the component type is open in the editor.

4.9.2 Opening component types from the task card

You can now open component types in the Components task card in the editor their the context menu (Open command).

4.9.3 Controls on the basic and link symbol

You can now also place controls on the basic and link symbol of component types. Where the component symbol design allows, you can therefore set values and display them directly on the symbol, without having to open their operating window first (Figure 4-64).

Figure 4-64: Component type with button on the basic symbol

4.9.4 Animations on the basic and link symbol

You can now apply animations to graphical elements used for creating the basic and link symbol.




4.9.5 Flipping graphics

When editing graphics – for example when editing the basic symbol – you can now flip the graphic horizontally and vertically using the corresponding icons ( , ) in the editor toolbar.

4.9.6 New byte data type

The byte data type is now available for discrete states. It allows you to store binary information or character strings of any length in components.

4.9.7 Free positioning of connectors

The coordinates of a connector are now displayed in the Properties dialog and can be edited there too. Unlike positions set using the mouse, positions entered manually are not aligned to the grid, nor are they restricted to the outline of the component. Therefore the coordinates do not necessarily have to be integer values either (Figure 4-65). Neutral connectors can also be placed arbitratily within the symbols area.

Figure 4-65: Position coordinates for a connector

In addition, the individual elements of a vector of inputs or outputs can now be positioned individually, although only if the vector has a constant rather than a variable dimension.

4.9.8 Scalability of graphics

The options for defining how graphics on the basic symbol behave if the component is scaled have been extended. Instead of a general setting for the basic symbol (Scale graphics), you can now specify on an individual basis whether a graphics object is to be scaled horizontally or vertically with the component. The same applies in the link view (Figure 4-66).




Figure 4-66: Settings for scaling graphics on components

4.9.9 New property: Proportionally scalable only

The basic symbol of a component type now has an additional property with which you can specify that the height and width of the component cannot be modified independently of one another but only proportionally, i.e. with a constant height to width ratio (Figure 4-67). However, this option can only be set if the component is also horizontally and vertically scalable.

Figure 4-67: Proportionally scalable only option

4.9.10 Using vectors with complex connection types in controls

You can now also use individual elements of a vector of signals with a complex connection type in controls. Indexing starts at 1 and the index should be added directly after the




connector name without brackets, as shown for example f

what's new in simit v7.1? · figure 4-28: diagnostics in the properties dialog for macro components...

Documents