ILMU AUTOMATION

Problem

Almost everywhere where products or materials are processed or worked, the temperature has a decisive influence on the quality of the final product and the course of the process respectively. It is thus necessary to record the temperature, to interpret its influence and to specifically react to changes in temperature using control technology.

Solution

The device combination of SIMATIC products and SIEMENS temperature sensors including measuring transducers is an excellent solution to the mentioned problem. In this application, a Pt100 sensor records the temperature of a measuring object and a SITRANS TK-L measuring transducer converts the sensor's measuring signal into an injected current which is supplied to an analog input of the compact CPU. The current temperature measurement value is displayed both numerically and as a bar chart on a TP170A touch panel.

Using the special STEP7 application software, which you can download (see below), it is additionally possible to ...

• define seven temperature ranges which are displayed on the touch panel and represented by DO bits. These bits can be used to trigger various user actions.

• display limit temperature violations requiring acknowledgement, react to them (in the program) and acknowledge them.

• provide the last insufficient or excess temperature with a time stamp.

The WinCC flexible configuration of the TP170A is integrated in the STEP7 project. The user interface languages German and English can be selected.

Downloads

Content of Downloads	Download
Documentation (German) Application Description
Documentation (English) Application Description
Code STEP7 Project

History

What points do you need to remember during the handling of micro memory cards?

Description:
This entry describes how to work with Micro
Memory Cards (MMC). A sample project is also included in Point 4. The
program shows how you can check whether specific data in a data block
is located in the load memory.

1. How should I save blocks or configuration data on the MMC which are transferred online to the CPU?

When you load blocks (OB, FC, FB, DB) and system data (from the
HW Config among other places, for example) into the CPU, they are automatically saved in such a way as to be safeguarded against voltage failure. The MMC is a flash EPROM medium.

2. Is there still need for the "Copy RAM to ROM..." function?

Not for saving blocks. However, if you have changed data blocks,
for instance if you have optimized control parameters, this function
also allows you to save the changed data values on the MMC (i.e. on the
load memory), which means that these new values are also available
following general PLC resetting (including in cases where the MMCs are
used as spare parts in another CPU).

Warning:
Please note carefully that the "Copy RAM to
ROM..." function affects all data blocks that are identified as
"unlinked". In the case of these data blocks, when the "Copy RAM to
ROM..." function is performed, the initial values in the load memory
(on the MMC) are overwritten with the actual values in the main memory.

For all data blocks, the initial values are taken as new values after
an overall reset. In the case of non-remanent data blocks the initial
values are also taken as new values after POWER OFF/ON or after
STOP/RUN operating modes.

If you want to save individual data blocks or data block
elements in the load memory, you can use SFC84 to do that. Here, please
note the following Point 3.

3. Can I save data blocks on the MMC via the user program, i.e. use the content as new initial values in the load memory?

CPUs with MMCs feature the SFCs 82, 83 and 84 for this purpose:

• SFC82 allows you to set up a data block in the load memory.
  
• SFC83 allows you to copy data areas from the load memory to the main memory, and
  
• SFC84 saves data areas in the load memory, i.e. it performs
  the function which is formulated in the question. However, bear in mind
  that the MMCs support a limited number of writing cycles (according to
  the manufacturer's details, 100,000 writing cycles are possible). For
  details about the memory concept of CPUs (load memory, main memory...
  ), please refer to the FAQ in Entry ID 7302326.

4. How can I check whether the data is really saved in the load memory with SFC84?

A check is possible if the data block is declared as "unlinked".

After copying an "unlinked" DB with SFC83 to the working area of
another DB you can make a check. In the load memory itself it is not
possible to access with a variables table or via "Monitor/control
variable", because access is made here to the working area. There is an
example of how to work with SFC83 attached. This illustrates how the
SFC 84 works.

Please also bear in mind that SFC 83 and SFC 84 work asynchronously.
This means that the SFCs might need several cycles to complete a job.

If the data block in the load memory has the attribute "unlinked", you
can make the check by loading the DB into the PG. Here, STEP 7
retrieves the current values from the load memory during each loading
process. In this regard, also refer to the FAQ in Entry ID 21688777.

Sample project:
Save the "MMC_S7_300_SFC83.zip" file
in a separate directory and then dearchive it. The S7 project then
unpacks with all the associated subdirectories. You can use the SIMATIC
Manager to open and process the extracted project.

MMC_S7_300_SFC83.zip ( 158 KB )

IMPORTANT
The sample program is freeware. Any user
can use, copy and forward this program FREE OF CHARGE. The authors and
owners of this program take no responsibility whatsoever for the
functionality and compatibility of this software. Use of the software
is at the user's own risk. Since this software is free of charge, there
is no warranty nor entitlement to error correction and hotline support.

5. When is it useful to compress an S7-300 CPU with MMC?

Deleting blocks on the CPU creates gaps in the load and main
memories. The gaps are not automatically closed when new or changed
blocks are transferred. When you compress, the gaps are closed by
copying the existing or new blocks. The procedure is comparable with
the defragmenting of hard disks in Windows.
You reduce cycle times
by compressing. That is why it is only useful to compress in order to
close a large number of gaps after blocks have been deleted frequently
in the CPU.

Compressing just after performing the "Load user program onto memory card" function is not
useful, because the MMC is deleted when the function is performed and
the blocks can be transferred without any gaps onto the MMC.

Warning:
Compressing, transferring and deleting blocks extends the cycle time of the CPU.

In the STOP operating mode you can perform compressing completely. In
the RUN-P operating mode, blocks that are open because of the running
program cannot be moved when compressing is performed.

-----------------------------------------------------------

Which memory cards can you use with a S7-300 CPU?

Description:
The following tables (Table 01 to Table 08) show the S7-300 CPUs and the memory cards to be used with them.
Here we distinguish between:

• MC (Memory Card)
• MMC (Micro Memory Card)

If you are doing an update of the operating system for the S7-318-2 CPU, you can use S7-400 memory cards, order number 6ES7952-1K... For details, please see Entry ID: 7286150.
 

List of Memory Cards (MC):
In normal mode, only the "short" memory cards (MC) can be used with S7-300 CPUs (with MC slot). Table 09 lists the order numbers of these memory cards.
 

More information is available in the manual "SIMATIC Automation System S7-300, CPU Data, CPUs 312IFM to 318-2 DP", sections 1.1.4 and 4.2 in Entry ID: 8860591.

List of Micro Memory Cards (MMC):
Table 10 lists the order numbers of the Micro Memory Cards (MMC).
 

QUESTION:
The analog values are transferred only in part or not at all. How can I clear this problem?

ANSWER:
If none or only part of the analog values are transferred, or the transferred values are incorrect, then this might have something to do with the length of the consistent data of the slave (affects S7-300/400 CPUs).
If more than 4 bytes (or exactly 3 bytes) are consistent over the entire length, then you must access the analog values of the slave with the SFCs 14 "DPRD_DAT" and 15 "DPWR_DAT". A description of the SFCs is given in the manual "System Software for S7-300/400 System and Standard Functions". The information on consistent data lengths of the PROFIBUS DP slave are given in the HW Config.
Procedure:

1. In the HW Config you mark the PROFIBUS slave.

2. Double-click the module from which you want to know which consistent areas it has. In the "Address/ID" tab of the "Properties - DP slave" window you can see the length over which the data is consistent.

What differences are there when configuring S7 connections?

Description:
In this description of how to configure S7 connections it is assumed that all the stations are in one S7 project.

Types of S7 connections:
With S7 connections you differentiate between bilaterally configured and unilaterally configured S7 connections.

Bilaterally configured S7 connections
You recognize bilaterally configured connections by the fact they they receive a connection ID at both endpoints. The partner ID can be identical for both connection partners, but doesn't have to be. The remote endpoint of the S7 connection created is entered automatically in the connection table on the partner side.

Unilaterally configured S7 connections
Unilaterally configured S7 connections are configured on the module that actively sets up the S7 connection. If an S7-300 or S7-400 station actively sets up the S7 connection, then you call communication blocks FB/SFB14 "GET" and FB/SFB15 "PUT" in the CPU's user program (client). You can use these for data communication via unilaterally and bilaterally configured S7 connections. You can only use the communication blocks FB/SFB12 "BSEND" and FB/SFB13 "BRCV" and FB/SFB8 "USEND" and FB/SFB9 "URCV" for data communication via bilaterally configured S7 connections.
In NetPro there is a connection table with all the configured communication connections. Unilaterally configured S7 connections have no entry in the "Partner ID" column of the connection table. This field remains empty in the connection table. No S7 connection is configured on the server and no communication blocks are called. The server is managed independently by the CPU's operating system and has resource 0x03. No system data is created for this in the connection partner.

Fig. 1: Bilaterally and unilaterally configured S7 connection

Summary:

• All S7 connections that have a connection ID at both connection endpoints are bilaterally configured S7 connections.

• S7 connections that have no partner ID are unilaterally configured S7 connections or have been created via "unspecified" S7 connections with resource 0x03.

Important:

• With bilaterally configured S7 connections you must load the configuration in both connection partners after creating the S7 connection.
• With unilaterally S7 connections you must load only the one station in whose connection table the S7 connection is shown.

Note:
In the sample S7 connection configuration given above all the stations are in one S7 project. You can also set up an S7 connection to an unspecified partner and the endpoints of these connections can be in different projects. More information on this is available in the Online Help of STEP 7:

• Configuring cross-project connections.
• Connection types for partners in other projects
• Creating cross-project subnetworks.

Keywords:
Connection configuration, S7-300, S7-400, SIMATIC, Connections, Creating a connection, Client, Server, Connection setup, NetPro

Instructions:
In order to reduce configuration work, parts of a project are often copied and inserted into a new project.
Here, tags and objects are copied, which are no longer used in the newly created project.

WinCC flexible provides a function which can be used to have these unused tags displayed.

In the "Edit" menu you select the command "Find in project...". In the window that opens you select the required search options.

For example, to find unused tags you select the "Filter" item. In the text list you select "Tag" as the object type.
Under the "In" item you specify the folder in which the search for the object type is to be made. This is particularly useful when there are multiple operator panels in the project.

Under "Reference" you select the subitem "Not used by" -> "All types". Then click the "Find now" button.

Now on the right you get a display of all the unused tags.
To delete them you select the tags concerned and right-click. A pop-up menu opens in which you select "Delete" to delete the marked tags.

( 37 KB )
Fig. 01

Keywords:
Delete tags

QUESTION:  
Can I copy a SIMATIC WinCC flexible project integrated in SIMATIC STEP 7 at file level? 

ANSWER:  
Copying of HMI projects integrated in STEP 7 at file level (e.g. with Windows Explorer via Copy/Cut and Paste) is not possible in combination with WinCC flexible. 

By copying of HMI projects integrated in STEP 7 (*.hmi) at file level you lose internal references from the WinCC flexible project to the the associated STEP 7 project. Then synchronization between the WinCC flexible project and the STEP 7 project is no longer possible.

When you attempt to open an HMI station copied at file level from the SIMATIC Manager, you get a message regarding access to STEP 7 information after opening the HMI station in WinCC flexible ES.

1. Proceed as follows if you want to copy a SIMATIC HMI station from a STEP 7 project:

• Open the STEP 7 concerned with the SIMATIC Manager.
  
  
• Start WinCC flexible via "SIMATIC HMI Station > Right-click on WinCC flexible RT > Open object".
  
  
• In WinCC flexible you select the menu "Project > Copy from STEP 7" to create a non-integrated HMI project from the SIMATIC HMI station.
  
  Note: 
  The original SIMATIC HMI station or the HMI project is retained in the STEP 7 project. 

Fig. 1: Creating a non-integrated HMI project

• You can then handle the HMI project created just like a normal HMI project.
   

2. Proceed as follows if you want to integrate back into STEP 7 a SIMATIC HMI station copied from a STEP 7 project:

• Open the HMI project concerned with WinCC flexible.
   
• In the menu "Project > Integrate in STEP 7" select the relevant STEP 7 project with a double-click.

Fig. 2: Integrating an HMI project

Fig. 3: Selecting the relevant STEP 7 project

• Now the HMI project not integrated in STEP 7 is integrated into the STEP 7 project selected.
  
  Note: 
  This function only inserts the operator panel located in an HMI project into a STEP 7 project. If you want to replace an existing HMI station, then the HMI station to be replaced has to be deleted in the SIMATIC Manager.
   
• After integrating the HMI station you have to check and possible modify the hardware configuration of the HMI station in the STEP 7 "HW Config" as well as the connection parameters in SIMATIC WinCC flexible via "Communication > Connections".

Keywords:
Copy, Paste, Cut, Move, File management, Integration

Project archiving and migration
If you wish to archive a WinCC flexible project, you can reduce the volume and file size significantly by archiving just the following project files. Please refer also to the notes at the end of the entry on migrating WinCC flexible projects (opening a WinCC flexible project that is based on a previous version).

Notes on migration
Opening a WinCC flexible project that is based on a previous version.
When you open a WinCC flexible ES project with more recent version of WinCC flexible ES, a message is displayed during the opening procedure indicating that the project to be opened has been created with a previous version of WinCC flexible.

( 25 KB )
Fig. 04

Acknowledge the message with the "OK" button and WinCC flexible automatically creates a backup file. The file is located in the same project directory as the remaining configuration.
You recognize the backup file generated by the names "Project_name.backup.hmi" and "Project_name.backup_log.LDF".

Example
MP370_Touch.backup.hmi, MP370_Touch.backup_log.LDF
You can archive these files elsewhere. They are not necessary for the WinCC flexible configuration.

Keywords:
Project archiving, Project file 

Sumber: http://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&lang=en&objid=21896449&caller=view