|
Name |
Value |
Internal value |
Internal value, type |
Default |
|---|---|---|---|---|
|
Module ID 1) |
Internal |
7005 |
WORD |
7005 |
|
Parameter length |
Internal |
8 |
BYTE |
8 |
|
Error LED / Failsafe function (Table Error LED / Failsafe function⮫ Further information) |
On |
0 |
BYTE |
0 |
|
Off by E4 |
1 |
|||
|
Off by E3 |
3 |
|||
|
On + failsafe |
16 |
|||
|
Off by E4 + failsafe |
17 |
|||
|
Off by E3 + failsafe |
19 |
|||
|
Process cycle time |
1 ms process cycle time |
1 |
BYTE |
1 ms |
|
2 ms process cycle time |
2 |
|||
|
3 ms process cycle time |
3 |
|||
|
4 ms process cycle time |
4 |
|||
|
5 ms process cycle time |
5 |
|||
|
6 ms process cycle time |
6 |
|||
|
7 ms process cycle time |
7 |
|||
|
8 ms process cycle time |
8 |
|||
|
9 ms process cycle time |
9 |
|||
|
10 ms process cycle time |
10 |
|||
|
11 ms process cycle time |
11 |
|||
|
12 ms process cycle time |
12 |
|||
|
13 ms process cycle time |
13 |
|||
|
14 ms process cycle time |
14 |
|||
|
15 ms process cycle time |
15 |
|||
|
16 ms process cycle time |
16 |
|||
|
Check supply |
Off On |
0 1 |
BYTE |
1 |
|
Fast counter |
0 : 10 2) |
0 : 10 |
BYTE |
0 |
|
I/O-Bus reset |
Off |
0 |
BYTE |
Off |
|
On |
1 |
BYTE |
Off |
|
|
1) With a faulty ID, the module reports a "parameter error" and does not perform cyclic process data transmission. 2) Counter operating modes ⮫ “Fast counter” |
||||
|
Setting |
Description |
|---|---|
|
On |
Error LED (S-ERR) lights up at errors of all error classes, Failsafe-mode off |
|
Off by E4 |
Error LED (S-ERR) lights up at errors of error classes E1, E2 and E3, Failsafe-mode off |
|
Off by E3 |
Error LED (S-ERR) lights up at errors of error classes E1 and E2, Failsafe-mode off |
|
On + Failsafe |
Error LED (S-ERR) lights up at errors of all error classes, Failsafe-mode on *) |
|
Off by E4 + Failsafe |
Error LED (S-ERR) lights up at errors of error classes E1, E2 and E3, Failsafe-mode on *) |
|
Off by E3 + Failsafe |
Error LED (S-ERR) lights up at errors of error classes E1 and E2, Failsafe-mode on *) |
|
*) The parameter Behaviour DO at comm. error is only analyzed if the Failsafe-mode is ON. |
|
IO-BUS reset after PROFINET reconnection
IO-BUS reset after PROFINET reconnection controls the behavior of PROFINET CI modules in relation to connected I/O modules (both safety and non-safety I/O modules).
-
IO-BUS reset after PROFINET reconnection = “On” resets and, thus, re-parameterizes all attached I/O modules. All internal I/O modules states are reset, including the related diagnosis information.
If the parameter is set to “On”, the following applies:
-
The bumpless re-start of non-safety I/O modules will not be supported. It means, for example, that non-safety output channels will go from fail-safe values to “0” values during the re-connection and re-parameterization time and after that go to new output values.
-
Safety I/O modules will be re-parameterized and re-started as newly started modules, which may not require their PROFIsafe reintegration, depending on safety CPU state, in the safety application.
-
-
IO-BUS reset after PROFINET reconnection = “Off” will not reset all attached I/O modules. It will re-parameterize I/O modules only if parameter change is detected during the reconnection. All internal I/O modules states are not reset, including the related diagnosis information.
If the parameter is set to “Off”, the following applies:
-
The bumpless re-start of non-safety I/O modules is supported (if no parameters are changed). It means, for example, that non-safety output channels will not go from fail-safe values to “0” values during the re-connection and re-parameterization time, but directly from fail-safe values to new output values.
-
Safety I/O modules will not be re-parameterized (if no parameters are changed). Thus, they may continue their operation, which may require their PROFIsafe reintegration in the safety application on the safety CPU, e.g., if PROFIsafe watchdog time for this safety I/O module has expired. Any reintegration of such safety I/O modules will be not only application specific but also PROFIsafe specific and depend on the safety I/O handling in the safety application.
-