×
Siemens Industry Online Support
Siemens AG
Entry type: FAQ Entry ID: 13769782, Entry date: 07/14/2011
(1)
Rate

What should you watch out for during configuration with GSD files for DPV0 and DPV1 slaves?

  • Entry
  • Associated product(s)
Configuration notes: DPV1 slaves provide DPV0 slaves with additional support in terms of acyclic data exchange between master and slave. For example, the DPV1 slaves can be used to read and write a data record in order to reassign parameters to a slave in RUN mode, for example. Alarms can also be set by a DPV1 slave, ensuring that the alarm-triggering event is dealt with in the master CPU. The alarm data is also evaluated when the CPU is in STOP mode. ...

Configuration notes:
DPV1 slaves provide DPV0 slaves with additional support in terms of acyclic data exchange between master and slave. For example, the DPV1 slaves can be used to read and write a data record in order to reassign parameters to a slave in RUN mode, for example. Alarms can also be set by a DPV1 slave, ensuring that the alarm-triggering event is dealt with in the master CPU. The alarm data is also evaluated when the CPU is in STOP mode.

The table below describes a few things to watch out for during the configuration of DPV0 and DPV1 slaves:

  1. Connecting DPV0 and DPV1 slaves to a shared DP master system
  2. Setting the PROFIBUS address via the "Assign PROFIBUS address" function in a PROFIBUS DP slave
  3. The PROFIBUS address requested for a slave cannot be set
  4. Projects with DP slaves which use functions from GSD revision 3
  5. Malfunctions caused by different versions of GSD files
  6. Importing an inconsistent GSD file
  7. Deletion of slaves from the hardware catalog
No. Notes on the configuration of DPV0 and DPV1 slaves
1

Connecting DPV0 and DPV1 slaves to a shared DP master system
The DPV1 and DPV0 slaves can be connected together to a DP master system. A distinction is made here between two situations:

  1. If "S7-compatible" is set as the DP mode for the DP master, both types of slave are operated as DPV0 slaves. DPV1 functions are no longer available to use. As a result, there is no longer a hybrid configuration as such.
  2. If "DPV1" is selected for the DP master, this facilitates hybrid operation of the two slaves types with their respective functional capabilities.

Please ensure that all the DP masters in your automation system use the same operating mode. If the CPU modules (CPU41x from V3.1) support this function, the DP masters can also be used with different operating modes.

Note:
Set the mode for your DP master in the properties for the DP interface ("Operating Mode" tab). If "S7-compatible" is selected as the DP mode, STEP 7 checks whether all the DP slaves can be reset to this operating mode. If a DP slave requires DPV1 functionality, DPV1 mode must be selected.

 


Fig. 01
2 Setting the PROFIBUS address via the "Assign PROFIBUS address" function in a PROFIBUS DP slave
In principle, while PROFIBUS addresses are being allocated to slave stations, the only device that should be on the PROFIBUS DP is the PC/PG as the master. Addresses can only be allocated with the following interfaces or modules:

MPI-ISA Card
MPI-ISA on board
CP5411
CP5511
CP5512
CP5611
CP5613
CP5614

The PC or TS adapter cannot be used for this purpose.

3 The requested PROFIBUS address for a slave cannot be set
If a certain or requested PROFIBUS address (e.g. PROFIBUS address 3) cannot be selected for a slave in the HW Config, even though this address is not being used by any CPU, CP or slave in the STEP 7 project, the probable reason for this is that a module with this address (e.g. PROFIBUS address 3) had already been used once in this project. This module had then been deleted, and STEP 7 will now no longer accept a new slave with the same PROFIBUS address. Another reason for this could be that the project is defective.

This address is also no longer available in the Properties for the PROFIBUS interface (DP slave).

 

Fig. 02

 

Remedy
Close your hardware configuration and reorganize your STEP 7 project in the SIMATIC Manager,

  • either with "File > Reorganize..."
  • or via "File > Save as..." together with the option "With reorganization (slow)".

The address area is thereby reorganized in the HW Config. Once the HW Config is reloaded, this address should be able to be allocated again.

4 Projects with DP slaves using functions from GSD revision 3
The new functions from GSD revision 3 are supported from STEP 7 version V 5.1 onwards. In the case of DP slaves with these functions, downward compatibility is not guaranteed with versions of STEP 7 prior to V 5.1. If these types of DP slaves have been configured with STEP 7 V 5.1, the project can only continue to be processed using versions of STEP 7 prior to V 5.1 in compliance with the following conditions:
  • The slave can only be configured in DPV0 mode.
  • In functionally modular devices, modules may only be inserted which are supported in the corresponding slots. This restriction is not monitored in versions of STEP 7 prior to V 5.1.
  • Modules which occupy more than one slot in the DP slave are split into individual modules. The module whose name begins with "????" and subsequent modules named "-->........" form a unit and may not be changed.
5 Malfunctions caused by different versions of GSD files
If newer GSD files within the STEP 7 project are replaced by older versions of GSD files (i.e. versions which are installed in the programming device or on the PC), the stations (slaves) might no longer be correctly identified. DPV1 functionality is not supported from GSD revision 3 onwards.

There is currently only restricted capability to identify the versions of GSD files because there is no secured version management for a GSD file. The GSD revision cannot be used for this. Corresponding version identification will only be introduced in GSD revision 6.

In any event, SIMATIC GSD files are upwardly compatible. However, avoid importing lower versions of GSD files than those installed on the PG/PC.

When a STEP 7 project is opened and the hardware configuration is uploaded, a warning is output if

  • the project includes a GSD file with a more recent GSD revision than that installed on the computer
  • the project includes a GSD file with the same GSD revision but with a more recent date than that installed on the computer.

Remedy
Using the "Options > Update catalog" function, the imported GSD files in STEP 7 are displayed in the hardware catalog.

Note
You can find further information in the Online Help for STEP 7 under the topic "Information about GSD Revisions".

6 Importing an inconsistent GSD file
If you import an inconsistent GSD file from a different manufacturer, a syntax error is output from STEP 7 version V5.2 SP1 onwards with the following error message:
  • "The GSD file (type file) D:\KUNDENPROJEKTE\GSD\PF00841.GSD has a syntax error. The DP slave described by this file can therefore not be entered in the hardware catalog."

The GSD file in question was accepted up to STEP 7 V5.2 without SP1. From V5.2 SP1 the GSD file is rejected if the length of "User_Prm_Data_Len" is preconfigured with a value of 0, and this is a DPV1 slave. Such GSD files are not consistent because a DPV1 slave must have at least 3 bytes of User PRM data. A corresponding check was added from STEP 7 V5.2 SP1 onwards; otherwise, parameterizations are generated which are not accepted by DPV1 slaves.

Remedy
The manufacturer of the GSD file must make appropriate changes to ensure that the GSD file works properly. In the GSD files you must replace the entry "User_Prm_Data_Len = 0" by

  1. specifying the "Max_User_Prm_Data_Len" (at least 3)
  2. and entering at least three bytes of parameter-assignment data (e.g.: "Ext_User_Prm_Data_Const(0) = 0x00,0x00,0x00").
7 Deletion of slaves from the hardware catalog
  1. In order to delete a slave from the hardware catalog, you require the name of the corresponding GSD file. Open the HW Config and insert the slave, which you wish to delete, in your hardware configuration.
  2. Double-click the slave in order to open the "Properties" dialog box and take note of the name of the GSD file (XML file).
  3. Close the "Properties" dialog box and the HW Config, too.
  4. Open the Explorer in Windows and navigate through the drive on which STEP 7 is installed until you come to the directory "<Drive>\Program Files\Siemens\Step7\S7DATA\GSD".
  5. In the pane on the right, delete the XML file which you took note of in No. 2. By deleting this GSD file, the slave is deleted from the hardware catalog.
  6. Open the HW Config and update the hardware catalog via the menu command "Options > Update catalog".

 


Fig. 03

Keywords
PROFIBUS standard, DP slave parameters 

 

Security information
In order to protect technical infrastructures, systems, machines and networks against cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art IT security concept. Siemens’ products and solutions constitute one element of such a concept. For more information about cyber security, please visit
https://www.siemens.com/cybersecurity#Ouraspiration.