What should you watch out for during configuration with GSD files for DPV0 and DPV1 slaves?
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:
- Connecting DPV0 and DPV1 slaves to a shared DP master system
- Setting the PROFIBUS address via the "Assign PROFIBUS address" function in a PROFIBUS DP slave
- The PROFIBUS address requested for a slave cannot be set
- Projects with DP slaves which use functions from GSD revision 3
- Malfunctions caused by different versions of GSD files
- Importing an inconsistent GSD file
- Deletion of slaves from the hardware catalog
|No.||Notes on the configuration of DPV0 and DPV1 slaves|
Connecting DPV0 and DPV1 slaves to a shared DP master system
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.
|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:
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).
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:
|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
|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 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.
|7||Deletion of slaves from the hardware catalog
PROFIBUS standard, DP slave parameters