About Step7.pdf

16

© RENAULT 2008 Origin : PEGI - Renault Page : 1 / 16

Checking a SIEMENS STEP7 project

GE29.EA.037 /B ________________________________________

Guide ________________________________________

Status Applicable Importante Note : This document has been translated from the french. In the event of any dispute, only th

french version is referred to as the reference text and is binding on the parties. Object Allow the project control engineers to check the software quality and the quality of the

backup of on SIEMENS STEP7 project.

Field of application Renault Powertrain plants Issuer 65940 - Control command and Robotics engineering Confidentiality Not confidential Approved by Function Signature Application date

A JOUAIRE Department head 65940 11/2008

GE29.EA.037 /B


Version history

Version Update Purpose of main modifications Author A 06/2007 Creation (1) N. Breuil B 11/2008 Adds OB 100 Block (1.2) and NetPro (1.7.2) Nicolas Breuil

Replaces GE29.EA.037 / of 08/2008 Availability Internally on Intranet: http://gdxpegi.ava.tcr.renault.fr

Externally on Internet: www.cnomo.com E-mail: [email protected]

Documents mentioned Regulations : International : European : French : CNOMO : Renault : Other international

documents :

Other external documents

:

Codification ICS : 25.040.01 Class E29 Keywords Step7, siemens, logiciel, vérification, automatisme, automation, chek liste, software Language English (1) Co-workers on the preparation of this document Site Service Name Site Service Name

CTR 65941 Vasseur Eric Cléon 65941 Rolland Alain

GE29.EA.037 /B


Table of contents

Page

Preamble....................................................................................................................................3

1 Checking the software quality (Rules of programming) .......................................................4 1.1 Checking the software version on the maintenance PG............................................................................ 4

1.1.1 Checking the version of STEP7....................................................................................................... 4 1.1.2 Checking the toolbox version........................................................................................................... 5

1.2 OB Blocks................................................................................................................................................... 6 1.3 Programming language.............................................................................................................................. 6 1.4 Language of the program........................................................................................................................... 6 1.5 PLC cycle time ........................................................................................................................................... 6 1.6 Structure of the archiving of a project ........................................................................................................ 7 1.7 Checking the configuration of the PG / PC in the project........................................................................... 8

1.7.1 By the project source ....................................................................................................................... 8 1.7.2 By NetPro......................................................................................................................................... 8

1.8 Controlling the mnemonics (Off line).......................................................................................................... 9 1.9 Checking the calling of the blocks (OFFLINE) ......................................................................................... 10

2 Checking the STEP7 backup .................................................................................................11 2.1 Offline ....................................................................................................................................................... 11

2.1.1 Controlling the hardware configuration .......................................................................................... 11 2.1.2 Controlling the network configuration ............................................................................................ 12 2.1.3 Checking the SDB.......................................................................................................................... 13 2.1.4 Block consistency........................................................................................................................... 14

2.2 ONLINE CHECK ...................................................................................................................................... 15

3 Check list.................................................................................................................................16

Preamble This document applies to all STEP7 projects (SIEMENS). It has two aims:

Check the software quality of a program STEP7, following the recommendations from Renault. Check that the backup of a STEP7 project is ready and easy to use by the maintenance.

At the end of the document, a checklist divided into milestones, listing all the points to be checked throughout the document. This check-list is available on an free file on the database of standards management.

GE29.EA.037 /B


1 Checking the software quality (Rules of programming)

1.1 Checking the software version on the maintenance PG. It is important to check that the version of STEP7 and TOOLBOX of the machine are compatible with the versions installed in the maintenance PG.

1.1.1 Checking the version of STEP7 On the PG, go to STEP7; Help menu; About…

The version on the PG has to be superior or equal to the version used by the supplier.

GE29.EA.037 /B


1.1.2 Checking the toolbox version In the PG, go to the Start / Simatic / Information

Enter the Installed Software menu

The version on the PG has to be superior or equal to the version used by the supplier.

GE29.EA.037 /B


1.2 OB Blocks Compulsory OB Blocks:

OB1: Main block OB82 and OB86: These blocks prevent the machine from switching to STOP in case of

hardware defect. They must be present, even empty, if the application contains a PROFIBUS DP diagnosis.

(Recommendation of Renault). They must be absent if no PROFIBUS DP diagnosis is programmed. (To avoid)

OB122 : This block must be present to prevent the machine from switching to STOP in case of defect of access to EP (input) / PA (output) devices.

OB100 : necessary with NC 840D for configure the MCP Panel.

Prohibited OB blocks:

OB85 and OB121: These blocks mask the programming errors. For this reason, they must not be loaded in the machine

1.3 Programming language The "contact" ( CONT) language must be used for any logical functions such as:

Management of the functioning mode Cycle animation Actuator command Defect detection

The language “list of instructions" (LIST) is useful for the analysis functions and data treatment.

1.4 Language of the program The project must be documented in the language of the final user country. Pay extra attention to the titles and the comments of networks.

1.5 PLC cycle time

In the example, the time of machine cycle is of 2ms.

The average machine cycle time should not exceed 50ms, to guarantee a response time below 100ms.

The response time of a PLC is a determining factor of the cycle time of a machine. To verify this, go to Target system \ Diagnosis/Setting \ Scan Cycle time (this is done "ONLINE").

GE29.EA.037 /B


1.6 Structure of the archiving of a project

Architecture with a single command system

In this example, we have two operations that must exchange information through a DP/DP gateway. There are two different networks. Every station must be separately archived.

Architecture with only one archive For some architectures, it is not possible to do separated backup

In this example, we have two operations that must exchange information via a direct PROFIBUS network. Both OP have to be in the same project and they must not have a common address.

Renault requests for an archiving structure of the projects with a single command system by archive.

Profibus Network

DP/DP gateway

Profibus Network

Profibus Network

GE29.EA.037 /B


1.7 Checking the configuration of the PG / PC in the project The integration of the PG in the STEP7 project remains the initiative of the supplier for installations

with several PROFIBUS networks for example The advantage is to connect the PG with the parameters of the installation network (speed, HSA,

profile) and thus to connect systematically in the most optimized way. Two possibilities to verify

1.7.1 By the project source In SIMATIC Manager, verify if PG / PC is configured. Double click on it to access the properties and verify the addressing in the Interfaces tab.

1.7.2 By NetPro Access NetPro and verify if PG / PC is configured. Verify the used addresses.

The address 0 (on MPI and PROFIBUS) is reserved for the PG as a diagnosis tool.

GE29.EA.037 /B


1.8 Controlling the mnemonics (Off line)

Addresses without symbols and unused symbols

In SIMATIC Manager, in the Options menu, select Reference Data \ Generate. Choose new generation.

When the generation is made, select Options \ Reference Data \ Display to start the tool. Then, select Addresses without symbol.

Redo the manipulation by selecting "Unused Symbols"

The table of the Addresses without symbols must be empty. Verify particularly that:

All the variables of type E, In, M, T and Z are well documented. All the OB, FC, FB and DB blocks are well documented. The table of Unused Symbols must be empty.

GE29.EA.037 /B


1.9 Checking the calling of the blocks (OFFLINE) All the blocks present in a STEP7 program must be called. It is thus important to verify that these blocks are called. To check the calling of the blocks, access Tools, select Reference data /Display, then select Program Structure.

If blocks appear without a call: The program is not correct, it must be corrected. Caution! In the case of a supplier standard program, there might be unused "optional"

blocks, thus uncalled. The supplier has to justify the absence of call.

GE29.EA.037 /B


2 Checking the STEP7 backup

2.1 Offline

Before starting the tests: Use the maintenance PG Use a backup copy dedicated to this use. Any problem found will have to be communicated to the supplier, as he only is authorized

to make the modifications.

2.1.1 Controlling the hardware configuration

In the main window, open HW-Config of the chosen project by clicking Hardware

Once entered in HW-Config, click on Station and Consistency check.

No coherence error can be accepted.

GE29.EA.037 /B


2.1.2 Controlling the network configuration If there are networks, it is necessary to verify them:

In HW-Config, access the NetPro menu, via Options, Configure Network

Once in NetPro, click on Network and Check consistency

No coherence error can be accepted.

GE29.EA.037 /B


2.1.3 Checking the SDB It is important to verify that the SDB come from the compilation of the HW config, and not from a copy of a project. This avoids any loss of hardware configuration. In simatic manager, open all the tree structure down to blocks and check the date of modification of the system data. Compare the date and the hour with that indicated in HW config / Station / Properties

If the date is the same, the project was compiled from HW config and not loaded from the machine. The project is correct (there can be a difference of a few seconds).

If the date and the hour in S7 Manager are: "year 2006" and "hour 149", we are sure that the SDB comes from the machine. The project is incorrect.

GE29.EA.037 /B


2.1.4 Block consistency

To check the consistency of blocks from SIMATIC Manager, right-click on Blocks, then select Check Block Consistency.

Start a full compilation of the program via « Compile all. »

Same blocks of the program cannot be recompiled if they have a protection "KNOW-HOW PROTECT" protection. Do not take into account the indication in that case.

For the CN 840D, some blocks generated, such as the FB15, DB1 and DB2, are referenced but non-existent. Do not take into account alert messages for these blocks.

Compile all

Warnings are acceptable, but not errors.

Remember to check the supplier didn’t left any shunts in the program. Generally M0.0 (always zero) and M0.1 (always 1)

GE29.EA.037 /B


2.2 ONLINE CHECK

To begin this part, you must have: Raised the possible reserves of the OFFLINE validation Verified the hardware configuration to avoid comparing data that are not up to date.

Comparing project / PLC blocks To start the comparison of blocks from SIMATIC Manager, select Blocks in the tree view then, in the Options menu, select Compare blocks.

Select ONLINE / OFFLINE and tick including SDBs, then start the comparison

At the end of the comparison: The list of blocks must be identical. All the blocks present in the project must be present in the

machine and vice-versa. In the case of a CNC, some blocks can be present only in the machine because they are created by

the system. These differences are normal: The system data blocs (SDB) must be identical The program blocs (OB, FC, FB) must be identical The data block (DB) relating can have same code differences but the times tamping must be identical

In the exception, in the case of a CN (Digital controller) , certain number of blocks can be present that in the automaton, because they are created by the system. These differences are normal:

Number of the Block Comment DB2 Message in 700 xxx etc.. DB10 Exchange DB11 GMF DB19 Particular signals DB2x DB Canal x DB3x DB Axe x FB15

GE29.EA.037 /B


3 Check list This chapter allows to check all the points mentioned throughout the document. It must be attached to

the acceptance document. Any non-conform point must be logged in the LUP.

Points to check § OK NOK NC

Checking the software quality. (Rules of programming) Checking the software version on the maintenance PG 1.1 OB blocks 1.2 Programming language 1.3 Program language 1.4 PLC cycle time 1.5 Structure of the project backup 1.6 Configuration of PG / PC in the project 1.7 Controlling the mnemonics 1.8 Checking the calling of blocks 1.9

Checking the STEP7 backup OFFLINE check

Before starting the tests:

Use the maintenance PG Use a backup copy dedicated to this use. Any problem found will have to be communicated to the

supplier, as he only is authorized to make the modifications.

2.1

Controlling the hardware configuration 2.1.1 Controlling the network configuration 2.1.2 Checking the SDB 2.1.3 Checking the consistency of blocks 2.1.4 ONLINE check 2.2 Comparing the blocks project / machine 2.2

NC : Not concerned

About Step7.pdf

Documents

Transcript of About Step7.pdf