LOGO! 8 - High performance at a low price

New features

• Eight devices with an onboard Industrial Ethernet interface in a space-saving design (4 MW) 

• Crystal-clear display with six lines and three selectable background colors 

• Optional LOGO! CMR2020 and CMR2040 communication module 

• Integrated web server for hassle-free programming via remote control, IWLAN, or the Internet

Source: Siemens.com

High performance at a low price

Compared with its predecessor, LOGO! 0BA7, the innovated LOGO! 8 logic module offers more functionality in its spacesaving design of only 4 MW, at lower costs. Eight basic devices with and without display and for different voltage ranges have the same range of functions, which makes it very easy to choose the required version. Externally, the crystalclear, perfectly readable display, which now features six lines with 16 characters each, catches the eye. The user now benefits from twice as many characters per notification than before, as well as three interchangeable background colors. For greater visualization demands, another text display can be connected to the integrated Industrial Ethernet interface. The module is programmed via Industrial Ethernet, eliminating the need for a special programming cable.

An outstanding feature of the new LOGO! is the integrated web server, which can be configured with no special programming skills and enables hassle-free and inexpensive remote control and monitoring via IWLAN or the Internet. The LOGO! Soft Comfort V8 software has been completely redesigned. Communications via Industrial Ethernet are now configured automatically in the network view. Linking of function blocks and transfers between the various programs are easily performed with drag and drop. Existing programs from older versions can be carried over directly, making it significantly simpler to migrate to LOGO! 8.

Siemens micro automation offers targeted and cost-effective solutions for minor automation tasks. The new LOGO! 8 logic module provides tailored, expandable solutions and enables communication via web server without HTML programming skills.

siemens.com/logo

Jika kamu tertarik untuk belajar PLC Siemens Logo! 8, silahkan Klik Disini!
Ada 4 link yang harus kamu ikuti untuk mengetahui lebih detail tentang PLC mungil ini.

Android App is available for Siemens Logo! Download here!

Read More

Service Pack 1 for STEP 7 V5.5 and STEP 7 Professional 2010

Download  of Service Pack 1 for STEP 7 V5.5

Installation requirements:

• STEP 7 V5.5
• STEP 7 Professional 2010 

Please also read the information (What’s NEW, special hints, etc.) which we have compiled for you in entry ID 52336355.

Customers with a valid Software Update Service agreement for STEP 7 will receive the DVD with STEP 7 V5.5 incl. SP1 automatically.

Customers with a valid Software Update Service agreement for STEP 7 Professional will receive the DVD with the STEP 7 Professional Edition 2010 Service Release 1 automatically. The SP1 for STEP 7 V5.5 is part of this Professional DVD (see entry ID 52336670 ).

If you wish to change to a new operating system, please note the following:

• It is not permitted to change to another operating system, if STEP 7 is installed already. Before you change the operating system, please be sure to uninstall STEP 7 and any possible STEP 7 option packages.
• Before you change the operating system the existing authorization / License Key must be saved to a floppy disk or USB stick with the program AuthorsW / Automation License Manager.
• If you wish to change to MS Windows 7 with 64 Bit with STEP 7 Professional, you require the STEP 7 Professional Edition 2010 SR1.

Customers without Software Update Service agreement can obtain the SP1 as follows:

1. DVD:  You can order the Trial License with STEP 7 V5.5 incl. Service Pack 1 on DVD.
   The order no. is: 6ES7810-4CC10-0YA7
   
   For the current STEP 7 Professional you can obtain a Trial License with the STEP 7 Professional Edition 2010 SR1. The DVD with the STEP 7 Professional Edition 2010 Service Release 1 also includes the SP1 of STEP 7 V5.5 
   The order no. is: 6ES7810-5CC11-0YA7
   
2. Free DownloadAs usual, we are offering a free download.
   
   
   Service Pack 1 for STEP 7 V5.5
   SIMATIC_S7_STEP7_V55_SP1.zip ( 813381 KB )
   
   This free download includes the SP1 for STEP 7 V5.5 and NCM.
   

Read More

How do you configure an S7-300 CPU as DP slave to a CP 342-5 as DP master?

Description
This entry explains the configuration of an S7-300 CPU as DP slave to a CP 342-5 as DP master as well as the programming of data exchange between DP master and DP slave.
Proceed as follows to configure an S7-300 CPU as DP slave to a CP 342-5 as DP master and program data exchange between DP master and DP slave.
6518938_configuration_en.pdf ( 1267 KB )
Download The STEP 7 project contains a sample program for calling FC1 "DP_SEND" and FC2 "DP_RECV" in the user program of the DP master. The load and transfer commands are used for data transfer in the user program of the DP slave. The load and transfer commands support consistent transfer of a maximum of 4 bytes.
non_consistent.zip ( 635 KB )
The STEP 7 project contains a sample program for calling FC1 "DP_SEND" and FC2 "DP_RECV" in the user program of the DP master and a sample program for calling system functions SFC14 "DPRD_DAT" and SFC15 "DP_WR_DAT" in the DP slave. You use these system functions for transferring more than 4 bytes consistently.
consistent.zip ( 636 KB )
KeywordsConsistent data transfer, Master-slave communication

Read More

Virus inside S7-PLC, Step7, WinCC. DB 890 and DB 8062

http://www.langner.com/en/index.htm
Stuxnet logbook, Sep 16 2010, 1200 hours MESZ

With the forensics we now have it is evident and provable that Stuxnet is a directed sabotage attack involving heavy insider knowledge. Here is what everybody needs to know right now.

Fact: As we have published earlier, Stuxnet is fingerprinting its target by checking data block 890. This occurs periodically every five seconds out of the WinCC environment. Based on the conditional check in code that you can see above, information in DB 890 is manipulated by Stuxnet.

Interpretation: We assume that DB 890 is part of the original attacked application. We assume that the second DWORD of 890 points to a process variable. We assume that this process variable belongs to a slow running process because it is checked by Stuxnet only every five seconds.

Fact: Another fingerprint is DB 8062. Check for the presence of DB 8062 in your project.

Fact: Stuxnet intercepts code from Simatic Manager that is loaded to the PLC. Based on a conditional check, original code for OB 35 is manipulated during the transmission. If the condition matches, Stuxnet injects Step7 code into OB 35 that is executed on the PLC every time that OB 35 is called. OB 35 is the 100 ms timer in the S7 operating environment. The Step7 code that Stuxnet injects calls FC 1874. Depending on the return code of FC 1874, original code is either called or skipped. The return code for this condition is DEADF007 (see code snipplet).

The known variations of the malware are specifically directed at Siemens WinCC and PCS7 Products.
Over the weekend of July 17-18, news broke on the “Computerworld” technology Web site about a virus attacking industrial automation giant Siemens’ WinCC and PCS7 industrial control human-machine interface/supervisory control and data acquisition (HMI/SCADA) systems.
The virus exploited Microsoft Windows operating systems when Universal Serial Bus (USB) memory sticks are inserted in a host computer and automatically loaded.

In response to a query from Automation World, Siemens Industry Inc. (http://www.usa.siemens.com/industry) spokesperson Michael Krampe issued the following statement:

"Siemens was notified about the virus that is affecting its Simatic WinCC SCADA (Supervisory Control and Data Acquisition) systems on July 14. The company immediately assembled a team of experts to evaluate the situation. Siemens is taking all precautions to alert its customers to the potential risks of this virus.

"Siemens is reaching out to its sales team and will also speak directly to its customers to explain the circumstances. We are urging customers to carry out an active check of their computer systems with WinCC installations and use updated versions of antivirus software in addition to remaining vigilant about IT security in their production environments."

Well-known industrial cyber-security expert Eric Byres and his team conducted a weekend analysis, and Byres has issued a statement and is offering a White Paper analysis. Here is his analysis:

“Over the weekend my team has been investigating a new family of threats called Stuxnet that appear to be directed specifically at Siemens WinCC and PCS7 products via a previously unknown Windows vulnerability. At the same time I also became aware of a concerted Denial of Service attack against a number of the SCADA information networks such as SCADASEC and ScadaPerspective mailing lists, knocking at least one of these services off line.

“As best as I can determine, the facts are as follows:
• This is a zero-day exploit against all versions of Windows including Windows XP SP3, Windows Server 2003 SP 2, Windows Vista SP1 and SP2, Windows Server 2008 and Windows 7.
• There are no patches available from Microsoft at this time (There are work arounds which I will describe later).
• This malware is in the wild and probably has been for the past month.
• The known variations of the malware are specifically directed at Siemens WinCC and PCS7 Products and hardware PLC S7-315 and S7-417.
• The malware is propagated via USB key. It may be also be propagated via network shares from other infected computers.
• Disabling AutoRun DOES NOT HELP! Simply viewing an infected USB using Windows Explorer will infect your computer.
• The objective of the malware appears to be industrial espionage and sabotage; i.e. to steal intellectual property from SCADA and process control systems. Specifically, the malware uses the Siemens default password of the MSSQL account WinCCConnect to log into the PCS7/WinCC database and extract process data and possibly HMI screens.
• The malware is infected PLC S7-315 and S7-417 via modified S7 DLLs.

• The only known work arounds are:
• NOT installing any USB keys into any Windows systems, regardless of the OS patch level or whether AutoRun has been disabled or not
• Disable the displaying of icons for shortcuts (this involves editing the registry)
• Disable the WebClient service

“My team has attempted to extract and summarize all the relevant data (as of late Saturday night) and assemble it in a short white paper called “Analysis of Siemens WinCC/PCS7 Malware Attacks” which I have posted on my website in a secured area that can be accessed from http://www.tofinosecurity.com/professio ... cc-malware .

“If you would like to download the white paper, you will need to register on the web site and I will approve your registration as fast as I can. I have chosen to keep the whitepaper in a secure area as I do not want this information to be propagated to individuals that do not need to know and might not have our industries’ best interests at heart. People who are already http://www.tofinosecurity.com web members do not need to reregister.”

ttp://www.eset.com/press-center/article/eset-analysis-worm-win32stuxnet-targets-supervisory-systems-in-the-us-and-iran/7609
ESET Analysis: Worm Win32/Stuxnet Targets Supervisory Systems in the U.S. and Iran

Read More

LOGO! AM2 RTD Module Simplifies Setup

The latest LOGO! AM2 RTD module makes it simpler for users to add a range of sensors. The new module provides improvements that include support of PT100 and PT1000 sensors while also letting users mix either PT100 temperature sensors or PT1000 Flue gas temperature sensors.
The LOGO! AM2 RTD is fully compatible with the existing products (LOGO! 24, LOGO24o and AM2 PT100) and will replace the predecessor products. The line simplifies setup: when new sensor types are connected, the modules provide automatic identification of the connected sensor when the expansion module starts up.

LOGO! modular is available in various versions for a variety of supply voltages (12 V DC, 24 V DC, 24 V AC, 115/230 V DC, 115/230 V AC), offering distinctive features such as R: Relay output and C: Clock/time switch. Some LOGO! Versions include operator keypad and display panel in one unit, streamlining system design. Up to 36 different functions can be connected at the click of a button or by means of PC software.

For more information on the LOGO! AM2 RTD, please click here.

Read More

S7-300/400 CPUs: Temperature Recording in the S7-CPU by Means of Pt100 Resistivity Thermometer and SITRANS TK-L Measuring Transducer

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

Version	Modification
07/2002	First edition (V1.0)
08/2006	Second edition (V2.0) complete revision and update

Filter criteria:

Hardware platform:	SIMATIC S7-300/S7-400
Software:	STEP 7
Entry contents:	Application Examples

Read More

S7-300 Memory Cards -- Product information -- Technical data

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)

CPU 312	Order no.	Type of Memory Card
CPU 312	6ES7 312-1AD10-0AB0	MMC  max. 4MB
	6ES 7 312-1AE13-0AB0	MMC  max. 4MB
CPU 312C	6ES7 312-5BD00-0AB0	MMC  max. 4MB
	6ES7 312-5BD01-0AB0	MMC  max. 4MB
	6ES7 312-5BE03-0AB0	MMC  max. 4MB
CPU 312 IFM	6ES7 312-5AC02-0AB0	No Memory Card
	6ES7 312-5AC82-0AB0	No Memory Card

Table 01
 

CPU 313	Order no.	Type of Memory Card
CPU 313	6ES7 313-1AD02-0AB0	MC  max. 512KB
	6ES7 313-1AD03-0AB0	MC  max. 4MB
CPU 313C	6ES7 313-5BE00-0AB0	MMC  max. 4MB
	6ES7 313-5BE01-0AB0	MMC  max. 8MB
	6ES7 313-5BF03-0AB0	MMC  max. 8MB
CPU 313C-2 DP	6ES7 313-6CE00-0AB0	MMC  max. 4MB
	6ES7 313-6CE01-0AB0	MMC  max. 8MB
	6ES7 313-6CF03-0AB0	MMC  max. 8MB
CPU 313C-2 PtP	6ES7 313-6BE00-0AB0	MMC  max. 4MB
	6ES7 313-6BE01-0AB0	MMC  max. 8MB
	6ES7 313-6BF03-0AB0	MMC  max. 8MB

Table 02
 

CPU 314	Order no.	Type of Memory Card
CPU 314	6ES7 314-1AE03-0AB0	MC  max. 512KB
	6ES7 314-1AE04-0AB0	MC  max. 4MB
	6ES7 314-1AE83-0AB0	MC  max. 512KB
	6ES7 314-1AE84-0AB0	MC  max. 4MB
	6ES7 314-1AF10-0AB0	MMC  max. 8MB
	6ES7 314-1AF11-0AB0	MMC  max. 8MB
	6ES7 314-1AG13-0AB0	MMC  max. 8MB
	6ES7 314-5AE03-0AB0	No Memory Card
	6ES7 314-5AE10-0AB0	MC  max. 4MB
	6ES7 314-5AE83-0AB0	No Memory Card
CPU 314C-2 DP	6ES7 314-6CF00-0AB0	MMC  max. 4MB
	6ES7 314-6CF01-0AB0	MMC  max. 8MB
	6ES7 314-6CF02-0AB0	MMC  max. 8MB
	6ES7 314-6CG03-0AB0	MMC  max. 8MB
CPU 314C-2 PtP	6ES7 314-6BF00-0AB0	MMC  max. 4MB
	6ES7 314-6BF01-0AB0	MMC  max. 8MB
	6ES7 314-6BF02-0AB0	MMC  max. 8MB
	6ES7 314-6BG03-0AB0	MMC  max. 8MB

Table 03
 

CPU 315	Order no.	Type of Memory Card
CPU 315	6ES7315-1AF02-0AB0	MC  max. 512KB
	6ES7 315-1AF03-0AB0	MC  max. 4MB
CPU 315-2 DP	6ES7 315-2AF02-0AB0	MC  max. 512KB
	6ES7 315-2AF03-0AB0	MC  max. 4MB
	6ES7 315-2AF82-0AB0	MC  max. 512KB
	6ES7 315-2AF83-0AB0	MC  max. 4MB
	6ES7 315-2AG10-0AB0	MMC  max. 8MB
CPU 315-2 PN/DP	6ES7 315-2EG10-0AB0	MMC  max. 8MB
	6ES7 315-2EH13-0AB0	MMC  max. 8MB
CPU 315F-2 DP	6ES7 315-6FF01-0AB0	MMC  max. 8MB
CPU 315F-2 PN/DP	6ES7 315-2FH10-0AB0	MMC  max. 8MB
	6ES7315-2FH13-0AB0	MMC  max. 8MB
CPU 315T-2 DP	6ES7 315-6TG10-0AB0	MMC  min. 4MB, max. 8MB
	6ES7 315-6TH13-0AB0	MMC  min. 4MB, max. 8MB

Table 04
 

CPU 316	Order no.	Type of Memory Card
CPU 316	6ES7 316-1AG00-0AB0	MC  max. 512KB
CPU 316-2DP	6ES7 316-2AG00-0AB0	MC  max. 4MB

Table 05
 

CPU 317	Order no.	Type of Memory Card
CPU 317-2 DP	6ES7 317-2AJ10-0AB0	MMC  max. 8MB
CPU 317-2 PN/DP	6ES7 317-2EJ10-0AB0	MMC  max. 8MB
	6ES7 317-2EK13-0AB0	MMC  max. 8MB
CPU 317F-2 DP	6ES7 317-6FF00-0AB0	MMC  max. 8MB
	6ES7 317-6FF03-0AB0	MMC  max. 8MB
CPU 317F-2 PN/DP	6ES7 317-2FJ10-0AB0	MMC  max. 8MB
	6ES7 317-2FK13-0AB0	MMC  max. 8MB
CPU 317T-2 DP	6ES7 317-6TJ10-0AB0	MMC  min. 4MB, max. 8MB
	6ES7 317-6TK13-0AB0	MMC  min. 4MB, max. 8MB

Table 06
 

CPU 318	Order no.	Type of Memory Card
CPU 318-2	6ES7 318-2AJ00-0AB0	MC  max. 4MB

Table 07

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.
 

CPU 319	Order no.	Type of Memory Card
CPU 319-3 PN/DP	6ES7 318-3EL00-0AB0	MMC  max. 8MB
CPU 319F-3 PN/DP	6ES7 318-3FL00-0AB0	MMC  max. 8MB

Table 08

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.
 

Designation	Order no.
Memory Card FEPROM 16 KB	6ES7 951-0KD00-0AA0
Memory Card FEPROM 32 KB	6ES7 951-0KE00-0AA0
Memory Card FEPROM 64 KB	6ES7 951-0KF00-0AA0
Memory Card FEPROM 128 KB	6ES7 951-0KG00-0AA0
Memory Card FEPROM 256 KB	6ES7 951-1KH00-0AA0
Memory Card FEPROM 512 KB	6ES7 951-0KJ00-0AA0
Memory Card FEPROM 1 MB	6ES7 951-1KK00-0AA0
Memory Card FEPROM 2 MB	6ES7 951-1KL00-0AA0
Memory Card FEPROM 4 MB	6ES7 951-1KM00-0AA0
Memory Card FEPROM 16 KB*	6ES7 951-0KD80-0AA0
Memory Card FEPROM 32 KB*	6ES7 951-0KE80-0AA0
Memory Card FEPROM 64 KB*	6ES7 951-0KF80-0AA0
Memory Card RAM 128 KB	6ES7 951-0AG00-0AA0
Memory Card RAM 256 KB	6ES7 951-1AH00-0AA0
Memory Card RAM 512 KB	6ES7 951-1AJ00-0AA0
Memory Card RAM 1 MB	6ES7 951-1AK00-0AA0
Memory Card RAM 2 MB	6ES7 951-1AL00-0AA0

Table 09
* These memory cards are designed for use in the extended temperature range.

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

Designation	Order no.
Micro Memory Card 64 KB	6ES7 953-8LF20-0AA0
Micro Memory Card 128 KB	6ES7 953-8LG11-0AA0
Micro Memory Card 512 KB	6ES7 953-8LJ20-0AA0
Micro Memory Card 2 MB	6ES7 953-8LL20-0AA0
Micro Memory Card 4 MB	6ES7 953-8LM20-0AA0
Micro Memory Card 8 MB	6ES7 953-8LP20-0AA0

Table 10

Read More

Transfer of analog values from and to the PROFIBUS DP slave

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.

Read More

S7-400 CPU 41x -- Configuring and programming communication -- Configuring the PROFIBUS interface

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

Read More

How can you delete unused tags or objects from a WinCC flexible project?

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

Read More

Copying HMI projects integrated in SIMATIC STEP 7 at file level

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

Read More

How do you archive projects in WinCC flexible and which files are required?

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

No.	Project archiving in WinCC flexible 2007 and WinCC flexible 2008
1	Standalone project (a WinCC flexible project not integrated in STEP 7) Start WinCC flexible ES and archive the project via the menu command "Project > Archive...". The project to be archived must not be opened during archiving. The ZIP file created contains only the two files required for restoring your project - "Project.hmi" and "Project_log.LDF". The next time you dearchive and open the project, the files deleted previously are automatically regenerated. ( 59 KB ) Fig. 01
2	WinCC flexible integrated in STEP 7 In the case of a project integrated in STEP 7, you use the archiving method of the SIMATIC Manager (File > Archive...). From STEP 7 version V5.4 SP2 onwards, the WinCC flexible files are automatically reduced to files required for restoring your project.  The next time you dearchive and open the project, the files deleted previously are automatically regenerated. If you are using STEP 7 V5.4 + SP1, please refer to the information on "Project archiving in WinCC flexible 2005 SP1, Point 2".

 

No.	Project archiving in WinCC flexible 2005 SP1
1	Standalone project (a WinCC flexible project not integrated in STEP 7) If just the WinCC flexible project is to be archived without information for the delta compile, then only the following files are required. ProjectName.hmi ProjectName_log.ldf The files are located in the relevant project directory. The next time you open the project, the files deleted previously are automatically regenerated. "Attachment 1" contains a breakdown of WinCC flexible files based on a sample configuration. Attachment 1: Project_Data_2005.zip ( 11 KB )
2	WinCC flexible integrated in STEP 7 The procedure depends on the version of STEP 7: Up to STEP 7 V5.4 SP1 If the WinCC flexible project integrated in STEP 7 is to be archived without information for the delta compile, you can delete the following files. All files with the name "Project_n_{{..............................}}.data" e.g. -> PROJECT_1_{{9f58e235-cb6e-40eb-829f-e23350eedaca}}.data Project_n.Device_1.fwx e.g. -> PROJECT_1.SIMATIC HMI Station(1).fwx The files are located in your STEP 7 project directory under "HmiES  > Devicename_n >" e.g. "HmiES  > PROJECT_1 >"  ( 41 KB ) Fig. 02 Then archive your STEP 7 project as usual. The next time you open the project, the files deleted previously are automatically regenerated. From STEP 7 V5.4 SP2 onwards From STEP 7 version V5.4 SP2 onwards, you can use the archiving method of the SIMATIC Manager (File > Archive...). The WinCC flexible files are automatically reduced to files required for restoring your project. The next time you dearchive and open the project, the files deleted previously are automatically regenerated.

 

No.	Project archiving in WinCC flexible 2004 / 2005
1	Standalone project (a WinCC flexible project not integrated in STEP 7) If just the WinCC flexible project is to be archived without information for the delta compile, then only the following files are required. ProjectName.hmi ProjectName_log.ldf The files are located in the relevant project directory. The next time you open the project, the files deleted previously are automatically regenerated. "Attachment 2" contains a breakdown of WinCC flexible files based on a sample configuration. Attachment 2: Project_Data_2004.zip ( 11 KB )
2	WinCC flexible integrated in STEP 7 If the WinCC flexible project integrated in STEP 7 is to be archived without information for the delta compile, then only the following files of WinCC flexible are required. GuidId.bin GuidTp.bin IdGuid.bin ProjectName.devices ProjectName.hmi ProjectName_log.ldf The files are located in your STEP 7 project directory under "HmiES  > Devicename_n >" e.g. "HmiES  > PROJECT_1 >"  ( 31 KB ) Fig. 03 The next time you open the project, the files deleted previously are automatically regenerated.

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

Read More