Description From STEP 7 V5.0 SP3 HF3 onwards you can reach ST stations online over and beyond subnet limits with the PG/PC, in order, for example, to load user programs or a hardware configuration or in order to execute test and diagnostic functions. You can connect a PG/PC at any place within the network and connect online to any stations which are reached through gateways.
The gateway from a subnet to one or more other subnets is in a SIMATIC station that has interfaces to the subnets concerned.
At least STEP 7 V5.0 SP3 HF3 is installed on the PG/PC for configuration and use of the S7 routing function.
An interface (Industrial Ethernet or PROFIBUS PC CP) is installed in the PG/PC to establish a connection to the gateway. You can use PROFIBUS PC CPs 55xx and 56xx. You can use any NDIS-compatible Ethernet network card (3COM, CP1613, for example) as Industrial Ethernet interface in the PG/PC.
The associated communications modules of the station support the S7 routing function.
The network configuration does not go across project boundaries.
Both the modules and the PG or PC are loaded with the configuration information that contains the latest "knowledge" about the complete network configuration of the project. Technical background All the modules associated with the gateway must receive information about which subnets can be reached over which routes (= routing information).
Note The lists below have been updated with the modules of the hardware catalog of STEP 7 V5.4 SP2. This means that older modules which support the S7 routing function are listed in the tables, but are not necessarily included in the hardware catalog of the latest versions of STEP 7.
SIMATIC S7-CPUs The list below gives an overview of the SIMATIC S7 CPUs that support the S7 Routing function.
What do I have to take into consideration when using the DPC2
starting with version SIMATIC NET CD 07/2001?
Below you can find complemental documentation for programming with
Parameters and options of DPC2 function calls which are not
supported in version 6.0 and 6.1:
Subnet addressing with Network_Address and MAC_Address is not
possible. Enter the value 0 for the parameters S_Type and D_Type.
The parameter Features_Supported is only supported as return
parameter. The parameters Profile_Features_Supported and
Profile_Ident_Number are not supported.
The parameters Instance, Reason_code and Locally_Generated are not
sent to the station. The return parameter Additional_Detail
contains a default value.
The parameters Slot_Number and Index will always be set to value
0. In addition, the return parameters Error_Decode, Error_Code_1
and Error_Code_2 of structure dpc2_error are not supported.
Calling the dpc2_get_event in asynchronous mode When calling dpc2_get_event in asynchronous mode, the return
value DPC2_NO_EVENT and in parameter *event_type_ptr the value
DPC2_OPEN_EVENT or DPC2_DATA_TRANSPORT_INT_EVENT are shown. What
meaning do these values have?
The functions dpc2_initiate and dpc2_data_transport are carried out
in two steps in asynchronous mode. The message Dpc2_OPEN_EVENT or
DPC2_DATA_TRANSPORT_INT_EVENT appears after running the first
internal intermediate step. The final acknowledgement is returned
in a subsequent dpc2_get_event call (in this case, the return
valuel of the function dpc2_get_event is not equal to
Error class DPC2_ERROR_BOARD_ACCESS A DPC2 function returns the value DPC2_ERROR_BOARD_ACCESS. The
parameter Error_Code of structure dpc2_error contains a detailed
error code that is not described in the DPC2 documentation. A
complete listing of the error codes follows (Hex values):
E_RESOURCES 0x012a /* no more system resources */
E_PAR_ERR 0x012e /* wrong parameter */
E_DPRAM 0x0132 /* no more DP RAM */
SCP_RESOURCE 0x00ca /* no more system resources */
EPROTECT 0x00ea /* no licence found */
SCP_DB_FILE_CLOSE_NOT_OK 0x00f1 /* NO_GLOBAL_DOS_MEMORY */
E_NO_HW 0x0310 /* MPI board not found */
E_HW_DEFEKT 0x0311 /* Problem with the hardware */
E_CNF 0x0312 /* wrong configuration parameter */
E_BAUDRATE 0x0313 /* wrong baudrate/wrong IRQ vector */
E_HSA 0x0314 /* wrong HSA configurated */
E_TS 0x0315 /* station adress already used */
E_OCC 0x0316 /* HW_Device alredy used */
E_INT_NOT_PROV 0x0317 /* IRQ not available */
E_INT_BUSY 0x0318 /* IRQ already used */
E_SAP 0x0319 /* SAP deactivate: SAP not used */
E_UNPLUGGED 0x031a /* not remote station found */
E_SYNI 0x031b /* Syni Error */
E_AMPRO 0x031c /* AMPRO 2 System Error */
E_NO_FILE 0x0320 /* DLL/VxD file not found */
E_NO_ENTRY 0x0321 /* loaded DLL has no entry point */
E_VERSION 0x0330 /* version conflict between SMC driver */
E_NO_SMC 0x0332 /* SMC doesn't answer (any more) */
E_ONLINE 0x0380 /* inlernal error with IOCTL Interface */
E_LOGDEV 0x0381 /* Configuration:log.device not in Registry */
E_L2DRIVER 0x0382 /* Configuration:L2DRIVER not in Registry */
E_L4DRIVER 0x0384 /* Configuration:L4DRIVER not in Registry */
E_SYSERROR 0x03FF /* Systemfehler, use GetLastError() */
Error class DPC2_ERROR_EVENT_NET: A DPC2 function returns the error class DPC2_ERROR_EVENT_NET as
value. The parameter Error_Code of structure dpc2_error contains a
detailed error code that is not described in the DPC2 documentation
(Table 3.2 "Error codes of class DPC2_ERROR_EVENT_NET" in the PDF
A complete listing of the error codes follows (Hex values):
Configuration: The sample GSD file "siem80b4.gsd" is available for the CP 5614. You have to change this GSD file to link the CP 5614 as a DP slave to a DP master system (e.g. S7-300 station).
You can create a valid GSD file for the CP 5614 with COM PROFIBUS V3.3. A demo version of COM PROFIBUS V3.3 is available in Entry ID: 135526.
You can install the valid GSD file in STEP 7, for example, in order to link the CP 5614 as a DP slave to a DP master system.
Proceed as follows to create the GSD file in COM PROFIBUS:
The sample GSD file "siem80b4.gsd" for the CP 5614 is located in the following directory: C:\Program Files\Siemens\SIMATIC.NET\dp\demo_gsd
The sample GSD file is included in the SIMATIC NET PC software delivery package.
Copy the sample GSD file "siem80b4.gsd" into the directory C:\COMPB33\GSD, which was created when COM PROFIBUS was installed.
Read in the sample GSD file via the menu "File > Read in GSD file".
In a new file, configure a default master system and the "CP 5614" as slave. After reading in the sample GSD file "siem80b4.gsd", the CP 5614 is among the slaves under "Miscellaneous".
Double-clickon the slave to open the "Slave Properties" dialog.
In the "Slave Properties" dialog you click on the "Configure" button. Here you can define up to 244 input/output modules. The size of the modules may be at most 16 bytes or 16 words.
Confirm the configuration and the "Slave Properties" dialog with "OK".
Mark the relevant slave in COM PROFIBUS. Then create a new GSD file via the menu "File > Create a GSD file". You can assign an identity number and any device designation.
If, in the "Create GSD file" dialog, you enable the function "Create GSD file with modular station structure", then you can use the slave universally. In this case, when configuring in STEP 7, you can always use the modules that you need and are not tied to a specific configuration. You can save the file in any directory of your choice.
The GSD file is now provided with the correct parameters (length of input and output areas, overall data length). Now you can install the GSD file in STEP 7.
Installation of the GSD file in STEP 7
Open the SIMATIC Manager and the editor for the hardware configuration.
Incorporate the GSD file created in COM PROFIBUS via "Tools > Install GSD files...". Update the hardware catalog via "Options > Update Catalog".
You should not have any windows open during this procedure.
Now the CP 5614 is located as a slave in the hardware catalog under "PROFIBUS DP > More FIELD DEVICES > General".
What are the options for connecting a PC station to Industrial Ethernet or PROFIBUS via the SIMATIC NET OPC server?
Configuration Notes: The SIMATIC NET OPC server is included in the SIMATIC NET PC software. With the SIMATIC NET OPC server, you can connect a PC station to S7 stations, S5 stations or third-party devices for data exchange via PROFIBUS or Industrial Ethernet.
The following communication services are available for communication via Industrial Ethernet:
S5-compatible communication and S7 communication
S5-compatible communication be used for data exchange with S7 stations, S5 stations and third-party devices. S7 communication can only be used for data exchange with S7 stations.
You need one of the following SIMATIC NET PC software packages to be able to use these communication services including SIMATIC NET OPC server:
SOFTNET S7 Lean - for up to 8 connections via normal Ethernet network cards, CP1612 or CP1512.
SOFTNET S7 IE - for up to 64 connections via normal Ethernet network cards, CP1612 or CP1512.
S7-1613 - for up to 120 connections via CP1613 (A2) or CP1623.
PROFINET IO controller
You need the following SIMATIC NET PC software to operate a PC station as PROFINET IO controller:
SOFTNET PN IO - for up to communication via normal Ethernet network cards, CP1612 or CP1512.
Fault-tolerant S7 communication You need the following SIMATIC NET PC software if you wish to configure fault-tolerant S7 connections for communication between S7-400H system and PC station:
S7-REDCONNECT - for communication via CP1613 (A2) or CP1623.
The following communication services are available for communication via PROFIBUS:
S7 communication S7 communication can only be used for data exchange with S7 stations. You need one of the following SIMATIC NET PC software packages if you want to use S7 communication including SIMATIC NET OPC server for data exchange:
SOFTNET S7 PB - for communication via CP5611 (A2), CP5621 or CP551x.
S7-5613 - for communication via CP5613/14 (A2).
FDL protocol The FDL protocol can be used for data exchange with S7 stations and S5 stations. You need one of the following SIMATIC NET PC software packages if you want to use the FDL protocol including SIMATIC NET OPC server for data exchange:
SOFTNET DP - for communication via CP5611 (A2), CP5621 or CP551x.
CP5613/5614 (A2) - here you do not need any other software, because the protocol driver is supplied with the hardware.
FMS protocol The FMS protocol can be used for data exchange with S7 stations and S5 stations. You need the following SIMATIC NET PC software package if you want to use the FMS protocol including SIMATIC NET OPC server for data exchange:
FMS-5613 - for communication via CP5613/14 (A2).
PROFIBUS DP slave You need the one of the following SIMATIC NET PC software packages to operate a PC station as PROFIBUS DP slave:
SOFTNET DP slave - for communication via CP5611 (A2), CP5621 or CP551x.
CP5614 (A2) - here you do not need any other software, because the protocol driver is supplied with the hardware.
More information is available in the manual of the DP Base programming interface in Entry ID 1653531. Note: On the S5 side, an IM308C or a CP5431 is used as DP master.
PROFIBUS DP master You need the one of the following SIMATIC NET PC software packages to operate a PC station as PROFIBUS DP master:
SOFTNET DP - for communication via CP5611 (A2), CP5621 or CP551x.
CP5613/14 (A2) - here you do not need any other software, because the protocol driver is supplied with the hardware.
More information is available in the manual of the DP Base programming interface in Entry IDs 1653531 and 25011749. Note: On the S5 side, an IM308C is used as DP slave.
Every communication uses different protocol layers of the ISO-OSI 7-layer model (e.g. transport layer). The protocol layers can be realized both through software on the communication processor and through software on the computer. If the computer is to do this task, then you have SoftNet card. If the work is done by the communication processor itself, then you speak of a HardNet card.
For the definition of whether you have a HardNet or SoftNet, therefore, it is important to know where the data exchange between the layers takes place. SoftNet communication processors simulate the required protocol via the computer and use the card only for the physical adapting of the signals to the bus system.
A HardNet card on the other hand has its own processor that handle the protocol processing independently. The driver software in the operating system (e.g. Windows NT) for this communications processor simply adds layers 6 and 7 to the protocol.
If you have to make a decision about which communications processor you want to use, then you must take the loading of the computer into account. If your computer is already heavily loaded by an application (e.g. WinCC), then it is always recommended to use a HardNet card.
Keywords: System requirements, Minimum requirements, Performance