ACTIVATE/DEACTIVATE PROFINET MASTER IN TIA PORTAL
1. Introduction
In some cases is possible we want to deactivate a master Profinet. For example, in a machine with interchangeable tools, if in every tool there is a master, to avoid the no master presence error in Tia Portal, could be interesting this feature.
2. Scope
This FB works for Siemens S7-1500 and S7-1200. Demonstrations has been made with BNI00HL (FW 1.3.0) with CPU 1511F-1 PN (FW V2.0).
3. Tia Portal
The Tia Portal FB to activate or deactivate a Profinet device is “D_ACT_DP”
“D_ACT_DP” is an asynchronous instruction.
The parameters are the following:
- REQ: Job trigger
- MODE:
- 0: Request current status of the master
- 1: Activate master
- 2: Deactivate master
- LADDR: Hw ID of the master
- RET_VAL: Return answer from FB, or if an error occurs while the instruction is being executed, the return value contains an error code
- BUSY:
- 1: The job is still active
- 0: The job was ended
Parameter RET_VAL:
|
Error code (W#16#...) |
Explanation
|
|
0000 |
Job completed without error. |
|
0001 |
The DP slave/PROFINET IO device is active (this error code is possible only with MODE=0). |
|
0002 |
The DP slave/PROFINET IO device is deactivated (this error code is possible only with MODE = 0. |
|
7000 |
First call with REQ= 0: The job specified with LADDR is not active; BUSY has the value "0". |
|
7001 |
First call with REQ= 1. The job specified with LADDR was triggered. BUSY has the value “1”. |
|
7002 |
Intermediate call (REQ irrelevant). The activated job is still active; BUSY has the value "1”. |
|
8090 |
• You have not configured a module with the address specified in LADDR. • For firmware versions < V2.9: You operate your CPU as I-slave / I-device and you have specified an address of this I-slave/I-device in LADDR. Note: As of firmware version V2.9 of the S7-1500 CPU, it is possible to switch the I-device functionality on or off locally in the program of the I-device CPU with the “D_ACT_DP” instruction. |
|
8092 |
The deactivation of the currently addressed DP slave/PROFINET IO device (MODE=2) cannot be canceled by being activated (MODE=1). Activate the component at a later time. |
|
8093 |
The address specified in LADDR does not belong to any DP slave/PROFINET IO device that can be activated or deactivated or the MODE parameter is unknown. |
|
8094 |
You have attempted to activate a device which is potential partner for a tool change port. However, another device is already activated on this tool change port at this time. The activated device will remain activated. |
|
80A0 |
Error during the communication between the CPU and the IO controller |
|
80A3 |
The DP master/PROFINET IO controller concerned does not support this function. |
|
80A4 |
The CPU does not support this function for external DP masters/PROFINET IO controller. |
|
80A7 |
A timeout occurred during activation: The remote device is unreachable or you have set the configuration time for central and distributed I/O too short. The status of the remote device is "activated", but it is not reachable. It therefore does not supply I/O data |
|
80AA |
The DP Slave/PROFINET I/O device was successfully activated and supplies I/O data, but is not error-free: The DP slave / PROFINET IO device has missing or incorrect submodules. |
|
80AB |
The DP Slave/PROFINET I/O device was successfully activated and supplies I/O data, but is not error-free: The DP slave/PROFINET IO device has at least one submodule with a parameter assignment error (Application Ready Pending). |
|
80AC |
The DP Slave/PROFINET I/O device was successfully activated and supplies I/O data, but is not error-free: The DP slave/PROFINET I/O device has at least one submodule with a maintenance diagnostics (Own State Maintenance Required, Maintenance Demanded or Maintenance Error). |
|
80C3 |
• Temporary resource error: The CPU is currently processing the maximum possible activation and deactivation jobs (8). • The CPU is busy receiving a modified configuration. Currently you can not activate/deactivate DP slaves/PROFINET IO devices. |
How is possible to identify HW ID?
