Description
The ET 200S and ET 200M distributed I/O systems may be used right into Zone 2. The ET 200iSP intrinsically safe distributed I/O system may be used right into Zone 1.

You can use the following PROFIBUS connectors for connecting the PROFIBUS network in Zone 2 (non-intrinsically safe PROFIBUS network).
 

30° outgoing cable unit (max. 1.5Mbit/s)	35° outgoing cable unit (max. 12Mbit/s)	90° outgoing cable unit (max. 12Mbit/s)
6ES7 972-0BA30-0XA0	6ES7 972-0BA41-0XA0	6ES7 972-0BA52-0XA0
-	6ES7 972-0BB41-0XA01)	6ES7 972-0BB52-0XA01)
-	6ES7 972-0BA60-0XA0	6ES7 972-0BA12-0XA0
-	6ES7 972-0BB60-0XA01)	6ES7 972-0BB12-0XA01)

¹⁾ PROFIBUS connector has a PG socket

For connecting an ET200iS in Zone 1, you must configure the PROFIBUS network in this area as intrinsically safe. Therefore, the above-listed PROFIBUS connectors are not suitable.

Use the PB FC Standard Cable IS GP (order number: 6XV1831-2A) and the PROFIBUS connector 6ES7 972-0DA60-0XA0 to connect the ET 200iSP intrinsically safe remote I/O system to the PROFIBUS network.

The IK PI catalog ("PROFIBUS" chapter) contains the technical data, order data and the order numbers of other PROFIBUS bus cables and bus connectors.

IK PI Catalog

Warning
In order to set up an intrinsically safe PROFIBUS segment, it is imperative to use the RS 485-IS coupler.
The manual for the RS 485-IS coupler is available in Entry ID 29306413.

PROBLEM:
DP configuration doesn't start up after a power supply OFF/ON

ANSWER:
Proceed as follows:

1. Switch on sequence : First switch the slaves on, then the master.
   At start-up the master parameterizes and configures all the slaves. Parameterization and configuration must be completed before further (productive) data traffic is possible. If a slave is not on the bus at the time of parameterization and configuration, then there can be no data communications with it.
2. Switch off sequence: First switch the master off, then the slaves.
   If you switch off the slaves first, then an I/O area access error (AAE) is registered on the CPU. This results in the CPU going into STOP with the I/O area access error. This means that just before the CPU recognizes the power OFF, another error occurs. It is then not possible for the CPU to start up again automatically after a subsequent power ON, because an "error" occurred just before. Since at start-up the CPU evaluates its previous operating status and this was STOP because of this "error", the CPU remains in the STOP status when the power is switched ON again. You must make a complete new start using the key switch in this case.

How to avoid the problems:

Either operate using the time relay or make a defined and coordinated manual switch-off to ensure that the above-mentioned conditions are met.

QUESTION:
What does Parameter DP Master System ID mean and where can you determine this?

ANSWER:
The DP Master System ID is a unique identification of a network assigned to the DP master.
This number is assigned by STEP7 when a DP master is configured in the STEP7 tool "H/W Config” and the associated PROFIBUS network.
With STEP7 V3.X and higher this number is entered in parentheses behind the designation "DP Master System (<<Number >>)”.
This designation is on the line that represents the DP line in the STEP7 tool "H/W Config”.

QUESTION:
If one master fails in my multimaster system, are the other systems still able to communicate?

ANSWER:
In your network there are multiple masters that each have access to multiple slaves. If one master fails, e.g. through power failure or another technical defect, then the following must be noted:
If the failure of one master in a multimaster system is due to a hardware fault, then under circumstances the complete network can be put out of action through a short-circuit on the bus line. In this case the fault must be cleared and the defective master removed from the network. If the failure of the master has no direct effect on the electrical properties (e.g. CP in STOP mode or power failure of the complete station), then the network can continue working.

If the master concerned is the last bus user in the bus network, then the following must be noted for PROFIBUS/MPI:
The open PROFIBUS line end must always have an active terminating element, i.e. one to which power is applied. This prevents reflections (noise or interference signals through periodic and/or random deviations) on the bus line. This is the only way for the other stations to be able to continue with unimpaired data communications. You can use the terminator that is included in the PROFIBUS connectors, but this has the disadvantage that if the complete station fails (e.g. through power supply failure), the network terminator is also lost. Then your complete network fails. It is better to use an external terminator (MLFB: 6ES7972-0DA00-0AA0), that is independent of the power supply of the automation systems.

Note:
You do not need a terminator for Industrial Ethernet.

If the failed master does not cause a bus short-circuit, then it does not need to be isolated from the bus. The communication of the intact master stations with their slaves is not affected.
The other masters can continue to have data communications with their slaves. The total cycle time is even shortened by the bus access time of the failed master.

Keywords:
Network nodes

QUESTION:  
Why is it not possible to start the PRB checker with the Windows language setting German (Switzerland)?

ANSWER:  
The PRB checker will not run with the Windows language setting German (Switzerland).

The following error message appears

Remedy: 
In the Windows language settings in Control Panel - Regional Settings, change the language setting to German (Germany).

The PRB checker can be downloaded free of charge under entry ID: 13884116.

QUESTION: -

ANSWER:

Under certain circumstances (e.g. error messages on the bus, bus errors) OPs might fail, as might other bus users connected to the distributed I/O. The OP logs off the bus or responds too late to a call telegram from the master and then has to be reparameterized by the master. There is massive interference of the bus traffic and failure of slaves, among other things, that had functioned perfectly up to this point in time.

This has been noticed frequently with the OP25, but this sort of error behavior still cannot be excluded with other OPs.

Experience has shown that the DP bus runs perfectly once one of the following parameters has been changed accordingly:

• Bus profile to "DP/FMS (Univ)”
• Increase maximum number of repeats (Retry Limit)
• Increase response time (T_slot)

Note that the bus system runs at a slower speed after these changes. You must use the trial and error method on the system concerned to find out which values to set.

PROBLEM:
Problems can arise if several systems each with their own power supply (central rack and distributed connection of expansion units) are connected to a common mains power supply and are switched on/off at the same time. Depending on the different system loads, the system power supplies switch the internal 5V system supplies at different times. This can affect the whole system and must be taken into account when configuring and programming. The effects on the on/off phase are varied and must always be observed separately.

The technical background and proposed solutions are given in the following.

ANSWER:
1. Switch-off phase

There are no problems if the central rack is switched off first (5V system supply) and then the expansion unit. In this case, upon power down the CPU goes into the STOP status and goes back into the RUN mode when the power returns.

If the expansion unit is switched off before the central rack, the CPU can pick up and store another error from the distributed expansion unit. Such an error can be "power fall in expansion unit" (PEU) or "time-out" (QVZ). For safety reasons the SIMATIC S5 system behavior in this case is such that upon return of power, the CPU goes back to the status it was in before power down. Since the CPU had registered an error (PEU or QVZ) just before the power down, it remains in the STOP status. The operator must then, for safety reasons, acknowledge the registered error by switching on the power at the mains source or by restarting the CPU.

Proposed solution:
The PEU signal can be switched off for distributed connections (can be evaluated in programming for CPU 945). In the case of an error, the CPU goes into the STOP status with QVZ and not with PEU. This time-out can be suppressed in programming with the OB23/24. But this has the effect that the CPU no longer recognizes a removed or defective module, for example. We propose the following solution to distinguish between a "true QVZ" and at QVZ caused by power down:

1. Call a function block in the OB23/24
2. Program a time loop in the function block. This time depends on the system and must be derived empirically (we propose 100...500 ms)
3. Program the effect for a "true QVZ" (e.g. STOP)

	L	KT	10.0	Time loop 100 ms
	SI	T1
MARKE	U	T1		Time loop
	SPB	=MARKE
	STP			Reaction to "true QVZ", e.g. STOP
	BE

Notes:

• Time loop -> Time difference between systems on power up
• If necessary, retrigger cycle time
• Reset outputs for time-critical applications

Program description:

If a QVZ (due to power down or "true QVZ") is recognized, the CPU branches into the OB23/24 and the time loop is processed. If the QVZ is due to a power down, the CPU goes into the STOP status during the time loop processing (normal program operation). No further errors are registered and upon return of power the CPU goes back into the RUN operating mode.

If it is a "true QVZ", the next STEP5 operation/sequence is processed once the time loop has elapsed. Here the user can program the reaction to a "true QVZ" (e.g. STOP status).

2. Switch-on phase

On powering up, the CPU registers the entire digital I/O configuration and stores it on a check track. In the cyclic program only the I/O is read and written for updating the process image that is stored on the check track. There are no problems if you power up the expansion unit first and then the central rack.

Proposed solution:
In the case of the AG 115U CPU modules (B version) you have the option of "programmable power-up delay". In this case the I/O configuration is read in only after the power-up delay has elapsed. A delay in the OB21/22 would be ineffective, because the check track has already been read in.

The above proposals solve the problems without any additional hardware costs. If running without errors, the CPU goes into RUN mode as soon as the power returns.

QUESTION:  
What are the conceptual differences when comparing PROFIBUS with PROFINET?

ANSWER:  
The following graphic illustrates the general synonyms of the most important devices with PROFIBUS and PROFINET. In the following table the synonyms of the individual components in context with PROFINET and in context with PROFIBUS are located.

 

Digit	PROFINET	PROFIBUS	Comment
1	IO System	DP-Mastersystem	subsystem
2	IO Controller	DP Master	superordinated device
3	IO Supervisor	PG/PC	device for engineering and diagnostics
4	Industrial Ethernet	PROFIBUS	subnet
5	HMI	HMI	operator interface system
6	IO Device	DP Slave	superordinated device

QUESTION:  
Is there an overview of the comparison between PROFINET and PROFIBUS?

ANSWER:  
As an introduction to PROFINET there is the PROFINET System Description (Entry-ID: 19292127) and the document PROFINET IO from PROFIBUS DP to PROFINET IO (Entry-ID: 19289930). These documents deal with the comparison of the communications technology and the necessary changes in the user program. This is due to the quantity structure that is partly enlarged in PROFINET IO.

The new blocks and system state lists (SSL) replace the previous versions and are for the most part compatible. They can be used equally well for PROFINET IO and PROFIBUS DP.

If you are only using PROFIBUS DP, in principle you can continue to use the usual blocks and system state lists for PROFIBUS DP. But it is recommended to switch to the new system and default functions in any case.

QUESTION:  
On a PROFIBUS master system, on which the connection among stations is implemented via Power Rail Booster (PRB), can I use S7 communication, MPI, FDL or FMS?

ANSWER:  
The use of above mentioned protocols for communication within a PROFIBUS network with PRB is possible. The PRB supports and transfers all kind of telegrams which comply with the PROFIBUS standard. However, some further explanations are needed, since all above mentioned protocols require the use of active stations, which may be configured as master or as slave. 

If all active stations are on the stationary side of the contact rail network, or if the connection between PRBs is implemented with cable (crane facilities, EMV loaded environment), then there are no restrictions. All PROFIBUS protocols can be used.

If there are active stations on both sides of the contact rail network, then, in case of a physical interruption of the connection, there may be disturbances of the communication (interruption of the rail through a lift of the contacts, too high transfer resistance of switch gears of the Power Rail Line, etc.).

This shall be explained with the example of a stationary control as DP master and several vehicles as active DP slave. The controls are connected via PRB in a contact rail network. If the communication between the master and the slave does stop physically due to a lift of the rail contacts, then the slave slips out of the logical token ring. The master only communicates with reachable slaves and exchanges usage data and tokens. The slave without connection to the contact rail waits a specific period of time, and then generates (according PROFIBUS standard) a token of its own, since it no longer observes any activity on the PROFIBUS. Hence, two bus systems are created, that run asynchronously to each other, and have one token (permission to send) each. If the slave, disconnected from the connection, receives contact to the master system again (rail contact snaps back into the rail again), then the active stations recognize a double token on the bus. All stations withdraw from the bus. The communication is disturbed. The PROFIBUS will be initialized automatically and all stations will be accepted to the token ring. The communication is secured again.

Summary: 
Therefore it is possible to use communication mechanisms of the S7 communication, MPI, FDL, or FMS, via a Power Rail Booster transmission line. However, contact interuptions, which cannot be excluded, lead to a creation of two tokens with subsequent, brief interruption of the communication. This needs to be taken into account when configuring the plant.

QUESTION:
What should you watch out for when changing from EN50170  to DPV1?

ANSWER:
The following document will help you with the change from EN50170 to DPV1.

 Leitfaden_e_0103.pdf ( 174 KB )    

Configuration Notes
The PROFIBUS Nutzerorganisation e. V. (PNO) (PROFIBUS User Organization) specifies the PROFIBUS RS485-IS as an intrinsically safe bus.

The fact that the PROFIBUS RS485-IS is intrinsically safe means that all the voltages, currents, inductivities and capacities occurring are limited by electrical means. This prevents ignitable sparks and thermal effects so that PROFIBUS RS485-IS can be used in areas where there is a risk of explosion.

The "PROFIBUS RS 485-IS User and Installation Guideline" specification is available for downloading at the following link: http://www.profibus.com
There you will find all the information required for selecting and interconnecting multiple bus nodes on an intrinsically safe PROFIBUS RS 485-IS segment.

The following products meet the requirements in the PROFIBUS RS 485-IS User and Installation Guidelines and can be used in an intrinsically safe PROFIBUS RS 485-IS segment.
 

The ET 200iSP can be used in the hazard zones 1/21 and 2/22. Here, implementation of PROFIBUS DP according to PROFIBUS RS 485-IS is via an RS 485-IS coupler.

More information on operating the distributed I/O ET 200iSP via an RS 485-IS coupler on the PROFIBUS RS 485-IS as DP slave is available in the manual "Distributed I/O Device ET 200iSP" in Entry ID: 28930789.

If you use only the products just listed in an RS485-IS segment:

• you fulfill the directives regarding explosion protection according to Communication 113 (2003) from the Physikalisch-Technischen Bundesanstalt (PTB / German Federal Bureau of Standards). You can obtain the PTB communication from a bookstore or directly from the publishers Wirtschaftsverlag NW, Verlag für neue Wissenschaft GmbH at
  http://www.ptb.de
• then it is possible to use data rates of up to 1500 kbit/s.

Configuration notes:
You can use the BT200 hardware tester BT200 (6ES7181-0AA01-0AA0) to check the:

• PROFIBUS DP cable
• RS485 interfaces on the PROFIBUS DP stations
• Availability of the DP slaves.

The following adapters are available as optional extras:

• Adapter for connecting the BT200 bus tester to M12
• Adapter for connecting the BT200 bus tester to ECOFAST
• Adapter for connecting to the 24 V DC ECOFAST in order to supply the station with 24 V DC during the station test

These adapters are available from:

KnorrTec
Kapellenbergstrasse 34
D-93176 Beratzhausen
Federal Republic of Germany
Tel: +49 (0) 94 93/ 9 51 96 90
Fax: +49 (0) 94 93/ 9 51 96 79
E-mail: info@knorrtec.de

Important:
The hardware tester BT 200 (6ES7181-0AA01-0AA0) cannot be used in PROFIBUS PA systems and PROFIBUS RS485-IS systems.

The connection adapters are not Siemens products. Siemens does not grant any warranty nor accept any liability for the proper function of these third-party products.

What is PROFIdrive:
PROFIdrive is a device profile developed by drive manufacturers to provide manufacturer-neutral standardization of the PROFIBUS interface of drives and thus minimize integration and commissioning time and effort. The FAQ describes the terminology of the common data objects of cyclic communication between controller and drive.

Cyclic data transmission messages
Cyclic data transmission messages have the following basic structure.

Fig. 1
 

The core consists of user data (PPO)

Parameter process data object (PPO)
The structure of the user data for the cyclic channel is defined in the PROFIdrive Profile version V2.0 and designated as Parameter Process data Object (PPO). Using the PPO the master (controller) accesses the slaves (drives) cyclically. The PPO is divided into two areas: PKW area and PZD area. The dividing into the two areas achieves decoupling in time. The PKW area is usually processed slower than the PZD area.

Fig. 2
 

PKW area
With the parameter ID value (Parameter-Kennung-Wert (PKW)) you can monitor and/or change any parameter in the converter. For example, you can read out faults or minimum/maximum limits. The PKW area consists of at least for words, the parameter ID (Parameterkennung (PKE)), the parameter index (IND) and the parameter value (Parameterwert (PWE)) that occupies two words. There are also PPO types that do not have a PKW area.

Fig. 3
 

 

Parameter attributes	Explanation
PKE	The parameter ID is always a 16-bit value and consists of the task or reply ID (Auftrags- bzw. Antwortkennung (AK)), a toggle bit for spontaneous messages (SPM) and the parameternumber (PNU). It has the following structure. Fig. 4   AK The task/reply ID comprises bits 12 to 15. In the task message (Master → Converter) AK is a task ID and a reply ID in a reply message (Converter → Master). In the PROFIdrive Profile version V2.0 the task IDs 0 to 9 are defined (e.g. 0 = no task, 1 = request parameter value, 2 = change parameter value [word] etc.). More converter-specific task IDs are possible. Refer to the relevant manual to see which task/reply ID your drive supports. SPM Bit 11 serves as a toggle bit for spontaneous messages for transmitting active parameters. PNU Bits 0 to 10 contain the number of the desired converter parameter.
IND	In cyclic communication the parameter index contains the subindex (also array subindex) in the higher value byte. The lower value byte is not defined in PROFIdrive Profile version V2.0 and can be assigned according to the converter used. Fig. 5   When editing parameters, the subindex transmits the required index of an indexed parameter. When editing a description element (AK = 4), the number of the desired element is transmitted.
PWE	The parameter value is always transmitted as a double-word. Only one parameter value can ever be transmitted in a PPO message. Fig. 6   A 32-bit parameter value consists of PWE1 (high value word, 3rd word) and PWE2 (low value word, 4th word). A 16-bit parameter value is transmitted in PWE2. In this case you must set PWE1 to 0 in the PROFIBUS-DP master.

PZD area
In the process data area (Prozessdatenbereich (PZD)) both control words and setpoint values (Master → Converter), and also status words and actual values (Converter → Master) are transferred. Unlike parameter transfer in the PKW area, in which the parameters to be transferred are defined in the message, the process variables to be transferred in the PZD area are defined by the PPO type or the converter. Likewise, the amount of process data depends on the PPO type or converter.

Fig. 7
 

Some mandatory PZDs have a predefined names:
 

STW:	(Steuerwort) Control word 1 (usually on PZD 1)
HSW:	(Hauptsollwert) Main setpoint (usually on PZD 2)
ZSW:	(Zustandswort) Status word 1 (usually on PZD 1)
HIW:	(Hauptistwert) Main actual value (usually on PZD 2)

After PROFIdrive Profile version V2.0 there are five PKW areas predefined, which differ with regard to the presence of the PKW area or the length of the PZD area.

Fig. 8
 

In PROFIdrive Profile version V3.0 you can also freely configure the cyclic data in addition to the predefined PPO types. For example, you can configure four PZD words in MICROMASTER 420 and eight in MICROMASTER 440/430. A PKW area can be configured regardless of the amount of process data.

Refer to the relevant manual for more information, e.g. which task/reply ID your drive supports. If this is available electronically, we recommend searching for "PWE", e.g. in the Operating Instructions: MICROMASTER PROFIBUS Optional Board (Entry ID: 6586565) or in the MASTERDRIVE: Compendium Motion Control (MC 1.66) (Entry ID: 23660019)

Description
The manuals below are available in Industry Online Support for the Diagnostic Repeater for PROFIBUS DP and for the RS 485 Repeater.
 

Manual	Repeater order number	Entry ID
Diagnostic repeaters	6ES7972-0AB00-0XA0 6ES7972-0AB01-0XA0	7915183
SIMATIC NET PROFIBUS networks Note The section entitled "Active Components for RS 485 Networks" gives you information about the RS485 Repeater.	6ES7972-0AA01-0XA0	1971286
RS 485-Repeater	6ES7972-0AA02-0XA0	48598071

QUESTION:
What are the options for communication between two IM151 CPUs?

ANSWER:
The ET 200S with the IM151 CPU can be used as DP slave, DP master (with DP master interface module MLFB: 6ES7 138-4HA00-0AB0) or in standalone mode. This provides you with the following options for communication:

1. MPI
1.1 S7 Basis Communication
1.2 Global Data Communication

2. PROFIBUS DP
2.1 Communication via an Additional DP Master
2.2 Communication via a DP Master Interface Module
2.3 Direct Data Exchange

3. Serial Communication

4. Creating PROFInet Components

1.1 MPI - S7 Basic Communication

With the ET 200S CPU (from MLFB: 6ES7 151-7AA10-0AB0) you can configure the internal interface as PROFIBUS or as MPI. If you choose the MPI configuration, the S7 basic communication services are available.

Fig. 1: Communication via a common MPI network in standalone mode

For communication via the MPI network as shown in Fig. 1 you can use the blocks "X_SEND", "X_RCV", "X_GET", "X_PUT" and "X_ABORT" of the S7 Basic Communication. The communication can be set up by both stations.

More information on these blocks is available in the STEP 7 Online Help (Mark block in block container> Press "F1") and in the manual "SIMATIC System Software for S7-300/400 System and Standard Functions" in Entry ID: 1214574.

1.2 MPI - Global Data Communication

With the ET 200S CPU (from MLFB: 6ES7 151-7AA10-0AB0) you can connect the internal interface both to a PROFIBUS network and to an MPI network.

For the connection via the MPI network shown in Fig. 1 you can also realize data exchange via global data. This communication can be set up by both stations.

The configuration of data exchange via global data is similar to the configuration of global data for CPUs of the S7 300 or S7 400 series.

Detailed instructions on configuring are available in the STEP 7 Online Help in the "Index" tab, keyword "Global Data Communication (Overview)".

2.1 PROFIBUS DP - Communication via an Additional DP Master

Communication between two PROFIBUS slaves without DP master (see Fig. 2) is not possible. This contradicts the PROFIBUS DP communications principle and is thus independent of the type of DP slave concerned.

Fig. 2: Networking the ET 200S CPUs via PROFIBUS DP without DP master

If both IM151 CPUs of the ET 200S are used as DP slaves, then you need a separate DP master (e.g. the integrated DP interface of an S7-300 CPU as shown in Fig. 3).

Fig. 3: Networking of the ET 200S CPUs via PROFIBUS DP with DP master

If data is to be transferred from one DP slave to another slave, then this has to be done by the DP master. The DP master reads the data out of the DP slave and writes it to the other slave. This communicationcannot be triggered by the CPU in the ET 200S.

2.2 PROFIBUS DP - Communication via the DP Master Interface Module

If there is a master interface module (implementation of IM151 CPUs 6ES7151-7AA10-0AB0 and higher possible) in one of the two ET 200S modules, then you do not need a separate master. The second IM151 CPU is then a DP slave on the master interface module of the first ET 200S (see Fig. 4).

Fig. 4: Networking the ET 200S CPUs via PROFIBUS DP with DP master

In this case, too, the communication can only be triggered by the DP master. Transfer of data from the ET 200S CPU that is connected as DP slave is not possible (exception: if you use the "Direct Data Exchange" function).

Note:
In versions 2 and 3 using the PROFIBUS DP network, data exchange via I/O access (e.g. L EW1 or T PAW6) or by calling system functions SFC14/15 can be made from the DP master concerned in each case.

2.3 PROFIBUS DP - Direct Data Exchange

Another option involves using direct data exchange (internetwork traffic). With this function you can exchange data between two DP slaves and between a DP master and a DP slave without having to make any special function call-ups in the program of the DP master or DP slave. The configuration is similar configuring the "Global Data Communication" function.

In the case of communication between two DP slaves however, you do need an associated DP master for each slave so that the PROFIBUS DP network required for direct data exchange can be set up (setup is as shown in Fig. 3). With the "Direct Data Exchange" function it is also possible to exchange data between two slaves that do not share a common master, but use the same PROFIBUS network.

Detailed information on "Direct Data Exchange" is available in the STEP 7 Online Help. Refer to Entry ID : 17660809 to find out whether your DP slave modules support the "Direct Data Exchange" function and to what extent.

3. Serial Communication

For low data transfer rates you can set up a serial point-to-point connection between two IM151 CPUs. This communication option depends on whether the ET 200S is being used as DP master, DP slave or in standalone mode. For this you only need the "interface module 1SI" (MLFB: 6ES7138-4DF*0-0AB0) in each ET 200S station.

4. Creating PROFInet Components

You can create PROFInet components for CBA (Component-based Automation) from the stations of STEP 7. The requirement here is that you have installed the iMap software package using the installation option STEP 7 AddOn.

Each PROFInet component has an interface, the PROFInet interface. With this interface the PROFInet components can communicate with each other and with the HMI system. The interface description is stored in a data block in STEP 7 - in the Interface DB. When you create the PROFInet component, the structure of the interface and the number and properties of the inputs and outputs are taken from this Interface DB.

In the case of intelligent slaves - like the IM151 CPU of the ET200S - the DP master does not access the connected inputs and outputs of the slave directly, but accesses a transfer area in the address area of the CPU. The input and output data from the transfer area of the Interface DB of the PROFInet component is transferred to the transfer area of the IM151 CPU. For this data communication the Copy blocks FC10 (PN_IN) and FC11 (PN_OUT) have to be programmed in the user program for STEP 7.

Fig. 5: Data communication between Interface DB and I/O address area

FC10 copies the data from the transfer area of the DP master with proxy functionality to the inputs of the Interface DB and FC11 copies the outputs of the Interface DB to the transfer area of the DP master with proxy functionality.

A proxy system consists of a PROFInet device with proxy functionality and all the PROFIBUS devices linked to it. The proxy functionality permits a PROFIBUS device to communicate not only with its DP master, but also with all the PROFInet communication nodes.

Note:
More information on this is available in the manual "Component-based Automation Creating PROFInet Components " (MLFB: 6ES7820-0CC03-0YX0), which is also in the Internet in Entry ID: 18400608.

Keywords:
Network configuration

Instructions:
If you print out the network topology determined by the diagnostics repeater from STEP 7, then in particular the larger networks are printed out on several DIN A 4 pages. 
You have three options of having the complete network printed out on just one page. 

Option 1
STEP 7 version V5.3 SP3 supports convenient printout of the network topology. If you have an earlier version, then proceed as described in options 2, 3 or 4.

Option 2
Many printers have a printer driver that supports the "Enlarge/Reduce" function. This permits you to print out a multipage document - here the network topology - on one page. However, the separate pages are often not printed joined up, but with a margin between them.

Option 3
The PDF Creator creates the complete topology as one page in the form of a PDF file. When you print out this PDF file with Acrobat Reader, this page is scaled to the current paper format of the printer. There are various other programs for printing out PDF files that have similar functions.

Proceed as follows:

• Install PDF Creator - you can download the software here:
  http://sourceforge.net/projects/pdfcreator/
• Have the network topology displayed and printed.
• For the printer you select the PDF Creator installed.
• Via "Printer Settings > Advanced" you select a fitting paper format for the topology. In the case of small topologies DIN A1 is most suitable, DIN A0 is better for larger topologies.
• Send off the printer job. Select the path for storing the PDF file.
• The PDF file produced can now be archived, printed or sent by e-mail. If you print it out, the file is scaled to the paper size. Using the option "Page Layout (N-up)" you can group together multiple pages.

Note:
The PDF Creator program is subject to the license conditions of the GNU-GPL, which you can read here:

http://www.gnu.org/copyleft/gpl.html

Option 4
There are various charged software tools that permit you to group together several pages on one printed page. One of these is the "FinePrint" software which we present here in brief by way of example.
FinePrint is installed like a proper printer. Then before starting the printing process you select the FinePrint "printer" instead of the "real" printer.

( 7 KB )
Fig. 1: Installed "FinePrint" printer

You can then edit the layout in "FinePrint" and start the final printout.

Note:
More information on this product is available at http://www.fineprint.com. Please also address your support inquires about FinePrint to the address given above.

QUESTION:  
Is it possible to transfer the registration key for an Amprolyzer installation to another PC?

ANSWER:  
Yes, the registration key for the Amprolyzer can be transferred to another PC.

Background
If the software is installed on PC 1 and you wish to use it on PC 2, for example, the license needs to be transferred from PC 1 to PC 2. However, the procedure for this is different to existing SIMATIC authorization procedures.

Procedure:
In order to transfer the registration from PC 1 to PC 2, the following procedure is recommended:

1. Install the Amprolyzer on PC 2 without entering the registration key.
2. Save the tool ID of the Amprolyzer from PC 2 (in a text file, for example, using the "Save as..." button). The "Registration" dialog can remain open.
   
   Fig. 1: "Registration" dialog ( 15 KB )  
    
3. Transmit the file with the new tool ID from PC 2 TO PC 1.
4. Deinstall the Amprolyzer on PC 1 via Start > Settings > Control System > Add/Remove Programs and select Amprolyzer.
   
   Fig. 2: Deinstallation of Amprolyzer on PC 1 ( 37 KB )  
    
5. Enter the tool ID which had been transferred previously for PC 2 from the text file in the "Tool-ID (target)" input field during the deinstallation routine.
   
   Fig. 3: Entering the tool ID in PC 1 ( 14 KB )  
    
6. You then receive a new registration key for the tool ID for PC 2.

Fig. 4: Saving the newly generated license key

7. Transfer the new registration key from PC 1 to PC 2.
8. The registration dialog can be opened again by restarting the setup routine (Start > Settings > Control System > Add/Remove Programs). (This is only required if the dialog has been closed beforehand). You can now enter the new registration key for the tool ID for PC 2, thereby registering the Amprolyzer on PC 2.
   
   Fig. 5: Entering the newly generated registration key on PC 2 ( 15 KB )  
   
   The following message then appears:

Fig. 6: End of registration

Following successful registration, you can start using your version of the Amprolyzer on PC 2 straight away.